The latest news from incident.io HQ

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.

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.

They're not kidding about the pace...

Going from 0 to shipping 2 features by the end of my first week

Keeping the codebase consistent with Pattern Parties

As a codebase evolves, it’s common to see some divergence in the design patterns within it.

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.

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.

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.

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.

How we leverage our Product Responder role to push our pace of development

At incident.io, Product Responder function plays a pivotal role in our ability to maintain a steady pace of development. Here, I'll highlight what the role is responsible for and explain how it makes us a better team.