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.
I moved a Next.js repo from ESLint and Prettier to Biome. Formatting was a clean win, linting was not. Here's the config I deleted and…
Prompt tone changes LLM output token count by up to 44%, per a new arXiv paper. Here is what I measured on my own prompts,…
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…
Server Actions in Next.js 16 queue one at a time, and revalidateTag no longer means what it used to. The two rules that cost me…
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…
Adding more few-shot examples can quietly make your LLM prompt worse. Here is what the over-prompting research found and how I size the example set…
A practical look back at PHP 8.4 well into 2026: which features I kept in production, from property hooks to the new array helpers, and…
Tailwind v4 makes container queries built in. Here is the card that broke in a narrow sidebar, the @container rewrite that fixed it, and when…
The built-in commands worth memorizing, how custom commands actually work in 2026, and the gotchas nobody documents: namespacing, argument indexing, and the SlashCommand tool.