We’re building the best way for your whole organization to respond, review and learn from incidents. This is where we talk about how and why.
What it meant for me to give away my Lego
If you join an early-stage startup, you'll probably have to give away your Lego one day. Here's what I learned when I had to part with mine.
Lisa Karlin Curtis
How we boost productivity with Raycast
At incident.io, we've used Raycast since V1. Here's how it's helped boost our productivity.
Charlie Revett
Taking the fear out of migrations
Migrations can be scary: here’s how we run migrations at incident.io to keep things simple and safe
Lisa Karlin Curtis
Game Day: Stress-testing our response systems and processes
Improving the way we respond to larger, more complex incidents.
Rory Bain
Intermittent downtime from repeated crashes
This is a technical write-up of an incident on Friday 18th November 2022 where we experienced 13 minutes of downtime from intermittent crashes.
Lawrence Jones
Making code-generation in Go more powerful with generics
Go 1.18 added generics to the language a few months ago. Here’s how we’ve combined generics with code generation to make our code safer and easier to read and write.
Isaac Seymour
Building a great developer experience at a startup
We’ve invested in our developer experience to help our team ship great a product at pace.
Lisa Karlin Curtis
Building Workflows, Part 1 — Core concepts and the Workflow Builder
Part one of a deep-dive into building our workflow engine, covering core workflow concepts and how they are used to power the Workflow Builder.
Lawrence Jones
Building Workflows, Part 2 – the executor and evaluation
Part two of the series lookin at the workflow executor, and concluding with an evaluation of the project in terms of developer time, extensibility, and quality of outcome.
Lawrence Jones
Stay in the loop: subscribe to our RSS feed.