They're not kidding about the pace...
Going from 0 to shipping 2 features by the end of my first week
Macey Baker
Keeping the codebase consistent with Pattern Parties
As a codebase evolves, it’s common to see some divergence in the design patterns within it.
Kelsey Mills
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.
Ben Wheatley
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.
Ben Wheatley
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.
Isaac Seymour
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.
Rory Bain
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.
incident.io
How our engineering team uses Polish Parties to maintain quality at pace
In a fast-moving company, quality cannot be delegated to a few individuals—it has to be a shared responsibility. One tool that helps us maintain our quality of work is Polish Parties. Here's how we run these crucial feedback sessions.
Leo Sjöberg
How we achieved pixel-perfect polish during our Status Pages launch
When we launched Status Pages, we wanted to challenge industry norms and push our design polish to new levels. As an engineering team, here's how we worked with our design team to make this happen.
Dimitra Zuccarelli
