Using context.Context to mock API clients
We've found a pattern to mock external client libraries while keeping code simple, reducing the number of injection spots and ensuring all the code down a callstack uses the same mock client.
Lawrence Jones
Breaking down complex projects into smaller, shippable increments
Mitigate the risks of delivering a complex project by shipping small pieces along the way.
Lisa Karlin Curtis
Building safe-by-default tools in our Go web application
Moving fast and breaking things is all well and good, but keeping our customer data safe isn't something we can compromise on. Find out how we do it!
Lisa Karlin Curtis
Deploying to production in <5m with our hosted container builder
Fast build times have a number of benefits, from reliability to developer happiness. We reduces our time to deploy to <5, and it's glorious.
Lawrence Jones
5 ways incidents made me a better engineer
Incidents are a great opportunity to gather both context and skill. We should all take advantage of them.
Lisa Karlin Curtis
Logs and tracing: not just for production, local development too
For a small initial investment, we've found a observability setup that works great for both production and local development. You should try it, too!
Lawrence Jones
Now you see me, now you don't: feature-flagging with LaunchDarkly at incident.io
At incident.io, we ship FAST. Find out how feature flags allow us to keep changes small and incremental while also hiding unfinished features from customers.
Sophie Koonin
One, Two, Skip a Few...
The other day, we started getting strange reports from some customers of incident.io. Their incident identifiers — unique numbers to identify each incident — appeared to have jumped unexpectedly.
Pete Hamilton
