Approfondimenti su pianificazione, produttività e creazione di software aperto

Slow CI is one of those things that grinds engineering team’s gears. Engineers wait longer for feedback, context-switching increases, and the temptation to batch changes grows, which only makes things worse. We spent a few weeks optimizing our GitHub Actions workflows and cut our PR checks from 30 minutes to 5 minutes. That’s an 83% reduction in wait time, achieved without sacrificing any test coverage or quality gates.

There wasn’t a single magic fix. We looked at where time was actually going and applied three principles: smart job dependencies, aggressive caching, and test sharding. Here’s what we learned.

On November 14th, we launched an updated design for the bookings page but quickly encountered usability issues. In this post, we share what we learned from the incident and the steps we're taking to improve our release process.

We are building infrastructure that must almost never fail. To achieve this, we move fast while shipping amazing quality software with no shortcuts or compromises. This document outlines the engineering standards that will guide us through 2026 and beyond.

A deep dive into how we detected, analyzed, and optimized poorly performing algorithms in a real production codebase.