API Design Principles: The Four I Enforce in Code Review
The four API design rules I actually enforce in code review: RFC 9457 error shapes, cursor pagination, idempotency keys, and additive-only changes.
The four API design rules I actually enforce in code review: RFC 9457 error shapes, cursor pagination, idempotency keys, and additive-only changes.
async-std is discontinued and most runtime comparisons miss the point: your dependency tree already picked Tokio. Here is how I checked mine, and when smol…
I migrated a working REST API to GraphQL and regretted it. Here's how I actually choose between GraphQL and REST in 2026, N+1 traps and…
PHP 8.4's asymmetric visibility lets a property be public to read but private to write. I deleted a stack of getters. Here's the syntax, the…
In FastAPI, async def is a promise not a superpower. Here's the def vs async def rule I use, the incident that taught me the…
The Go error handling patterns I actually ship in 2026: wrapping with %w, errors.Is vs errors.As, and killing the log-and-return anti-pattern.
How I moved a Go backend from zap to the stdlib log/slog package, the handler config I use in prod, and what I quietly miss…
I ran Laravel queues on queue:work + supervisord for two years, then a 3am alert made me switch to Horizon. Here's the config that actually…
A year of shipping PHP 8.4 property hooks in production: what actually replaced my old methods, where they made things worse, and the gotcha I…
TypeScript is structural, which is fine until two strings mean different things. Here is the branded types pattern I use to stop shipping ID mix-ups.