5 Quick Links for Devs: Week 12, 2026
How I'm Productive with Claude Code
A practical walkthrough of how removing friction (automated PRs, sub-second rebuilds, parallel worktrees) transforms you from "person who codes" into "manager of agents who code." The real productivity unlock isn't just having AI write code, but building the plumbing—like automated PRs and sub-second rebuilds—that keeps you in a flow state.
Reports of code's death are greatly exaggerated
While everyone is busy proclaiming the death of code in favor of "vibe coding," I think they're missing the point: a sufficiently detailed spec is code, and these tools just help us reach new levels of abstraction. We shouldn't use AI to ship more slop; we should use it as a tool to master complexity and build the kind of elegant, precise poetry that makes programming fun in the first place.
No Semicolons Needed
A surprisingly deep dive into how 11 different languages handle statement termination without explicit semicolons — from Python's strict indentation to JavaScript's famously cursed ASI rules to Gleam's elegant grammar design. If you've ever been curious about the design decisions lurking behind something as mundane as a newline, this is a great read. Personally I like semicolons even if they aren't needed :)
The Three Pillars of JavaScript Bloat
Identifies the three main culprits behind npm dependency bloat: legacy runtime support nobody needs anymore, atomic "one-liner" packages that were supposed to be reusable building blocks but mostly aren't, and ponyfills that have long outlived their usefulness. The e18e community and tooling mentioned here are worth keeping an eye on if you care about keeping your dependency tree sane.
To be a better programmer, write little proofs in your head
Matthew Prast’s thesis is that stronger programmers silently prove things to themselves while they code, checking invariants and monotonic progress before the computer has a chance to complain, and that getting good at this is what separates "works on the first try" from "works after six debug cycles." If your code is hard to reason about mentally, it’s probably a sign that you need to subdivide those units of work into something more manageable.