engineering
Most APIs treat errors as a status code plus a sentence. The APIs customers love treat errors as a recovery surface that tells them exactly what to do next.
engineering
Common Table Expressions make complex SQL readable. They also have subtle performance implications, especially around the optimization fence and recursive evaluation, that the readability sometimes obscures.
engineering
Most APIs handle starting work well and finishing work well. The middle case (telling them to stop) is where the design tradeoffs get interesting, especially when the operation has already been partly committed.
engineering
Postgres pages are 8KB, but rows can be much larger. The Oversized-Attribute Storage Technique handles this transparently, with performance and operational implications most teams never inspect.
engineering
Standard cursor pagination assumes a linear ordered list. Tree, graph, and hierarchical resources break that assumption, and the patterns that handle them well are not obvious extensions of the flat-list case.
engineering
The read-modify-write pattern is one of the most common concurrency bugs in production code, and it almost never shows up under low load. Three correct patterns exist that prevent the bug, and each fits a different operational context.
engineering
Most APIs conflate quotas and rate limits, returning the same 429 status for both. The distinction matters because the right response from the customer is different in each case, and conflating them produces support tickets about charges that customers cannot diagnose without reading source cod
history
The crane is one of the oldest continuous engineering traditions, with Roman treadwheel cranes that lifted 6000 kilograms persisting essentially unchanged through medieval cathedral construction and only being substantively superseded in the late 19th century. The history reveals how stable an
history
For most of human history, time was a local phenomenon. The day was divided into hours by sundials whose calibration depended on latitude and season. The night was divided by water clocks whose flow rates depended on water temperature and viscosity. Monasteries kept time by candle and oil lamps that
engineering
Search shows up early in the life of most SaaS products. A customer wants to find an invoice by the customer name on it. A team wants to filter feature flags by partial substring of the description. A developer wants to grep through captured webhook payloads. The reflexive answer is
engineering
The standard webhook playbook assumes a desktop or server consumer. The receiver has a stable public URL, persistent network connectivity, and a server-side application that can be relied on to acknowledge events within a few hundred milliseconds. Mobile clients break every one of these assumptions. The phone is behind NAT
engineering
Most teams reach for a denormalized column the same way every time. A new query needs to filter by lowercase email, or by month-of-creation, or by full-name-concatenated. The team adds a column, writes a backfill, updates the application to populate it on every insert and update, and adds an index.