Forays in Fancy Formatting
At incident.io, our raison d’etre is making it as easy as possible to handle incidents. So we want to make it as easy as possible to communicate in a rich way in incident summaries and updates. If you can emphasise certain things, or create a list, or @mention people, it’ll be easier for people to take in important information and easier to get that information to the people who need to see it.
Pip Taylor
Behind the curtain: figuring out a gnarly user experience
We recently shipped Configurable Forms which introduced the ability to control the layout and content of your incident forms in a single place. In this post, we’ll take a look behind the curtain at the process we went through to build a really great editing experience for our users.
Lisa Karlin Curtis
Engineering nits: Building a Storybook for Slack Block Kit
We care a lot about the pace of shipping at incident.io, and we also build lots of UIs inside Slack. Slack previews lets us collaborate on designing these experiences much more quickly.
Lawrence Jones
They're not kidding about the pace...
Going from 0 to shipping 2 features by the end of my first week
Macey Baker
Keeping the codebase consistent with Pattern Parties
As a codebase evolves, it’s common to see some divergence in the design patterns within it.
Kelsey Mills
Clouds, caches and connection conundrums
During a recent infrastructure migration into Google Cloud, we kept running into a pesky issue without a clear cause. Here, we dive into the twists and turns we took to finally figure out what the smoking gun was.
Ben Wheatley
Practical guidance for getting started as a Site Reliability Engineer
Here are a few strategies that might help you build up context, find the problems that really matter and turn these into a plan of action.
Ben Wheatley
Integrating the SWR library with a type-safe API client
Once API responses in our app are loaded into the cache, we don’t need to wait to refetch them if another page needs them.
Isaac Seymour
We used GPT-4 during a hackathon—here's what we learned
We learned a lot about using OpenAI and which things to keep an eye on to decide when it’s worth revisiting.
Rory Bain
