Stay up to date with practical insights on backend engineering, system design, and building reliable software.
Every API change is either backward compatible or a breaking change. Breaking changes require a new version. The versioning strategy and deprecation process determine whether version upgrades are painful or routine for clients.
Read moreJava's collection library has obvious defaults and non-obvious tradeoffs. The complexity numbers in the Javadoc tell part of the story — cache locality, memory overhead, and access patterns tell the rest.
Read moreCompletableFuture makes async composition possible in Java, but its API surface is large and the error handling semantics are non-obvious. Here are the patterns that produce maintainable async code and the pitfalls that produce callback soup.
Read moreSidekiq makes background job processing look simple until you hit retry storms, lost jobs, and race conditions. Here are the patterns that prevent those problems before they reach production.
Read moreRuby gives you three ways to package callable code, and most developers cargo-cult the choice. Here's a precise breakdown of the differences that actually affect behavior in production code.
Read more