The latest news from incident.io HQ

Why we chose JavaScript over CEL

A look into why we chose plain Javascript over CEL expression evaluation for our Catalog importer tool.

Running projects for AI features

In this article, Aaron the Technical Lead for the Post-incident team highlights the differences of running projects for AI powered features

Finding relationships in your data with embeddings

Spotting relationships in your data can be hard especially when that data is free text. Here's how we used LLMs and vector embeddings to quickly search through our data for similar topics and even concepts.

Building a GPT-style Assistant for historical incident analysis

What looks like making GPT-style assistant in a little over a month

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.

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!

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, analysing compiler performance and feeding an AI model the data until we had an answer.

Engineering nits: Generating code faster

As our app grew, our codegen got slower and slower. Here's how we made it 97% faster.

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.