Building a GPT-style Assistant for historical incident analysis
What looks like making GPT-style assistant in a little over a month
Teddy Aristide Necsoiu
Lessons learned from building our first AI product
If you're thinking of adding AI to your product, this is everything you should know in advance.
Milly Leadley
Debugging Go compiler performance in a large codebase
In a big Go codebase, compiling all that code can get slower over time. This is how I figured out some bottlenecks and made our builds much faster!
Isaac Seymour
Tracking developer build times to decide if the M3 MacBook is worth upgrading
When our CTO said "I'll upgrade your MacBook if you can prove it's worthwhile", we embarked on a journey including (re)building a Go hot-reloader, instrumenting developer builds, analyzing compiler performance, and feeding an AI model the data until we had an answer.
Lawrence Jones
Engineering nits: Generating code faster
As our app grew, our codegen got slower and slower. Here's how we made it 97% faster.
Isaac Seymour
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.
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
