Stay up to date with practical insights on backend engineering, system design, and building reliable software.
Fetching rows and aggregating in application code is slower, uses more memory, and is harder to maintain than letting the database aggregate at the source — yet this pattern persists because developers reach for familiar imperative constructs instead of SQL aggregations.
Read moreSome practices are context-dependent — they make sense for certain team sizes, certain stages, certain domains. Others are close to universal. Here's the short list I push for regardless of where I land.
Read moreRemote work sounds simple—just a laptop and internet. In reality, the right tools are what make everything actually work.
Read moreSome performance problems are invisible in staging, invisible in load tests, and only surface under the specific combination of data, concurrency, and access patterns that real users produce. Here is how to find them before they become incidents, and how to diagnose them when they do.
Read moreShipping code without a review might feel fast and efficient—but it’s a trap. One missed bug can ripple through your system and your team.
Read more