Zalt Blog

When AI takes the grunt work, where your people go next decides whether it pays off. Cut the freed capacity and you bank a one-time saving anyone can match. Redeploy it into judgment, relationships, and growth and you build an edge that compounds. The automation is the easy half. Redeployment is the return.

Addy Osmani's Beyond Vibe Coding argues you should be the editor-in-chief of your AI-generated code, not a passenger. Here's an honest review: who it's really for, what it gets right, and where it just repeats itself.

The context your AI is missing is the knowledge nobody wrote down: the exceptions, the unwritten rules, the hard-won cautions your best people carry in their heads. Capture that tribal know-how and an ordinary setup starts producing work that feels expert. Skip it and the best model still answers like a first-week hire.

What's actually inside Gene Kim and Steve Yegge's Vibe Coding book? Four parts, a FAAFO framework, and refreshingly honest stories about AI agents deleting tests and nearly wiping out weeks of work. Here's the real breakdown.

When one agent orchestrates a whole AI stack, you stop wiring pieces by hand and start thinking in terms of a single control tower for your system 🧠

Building complex graph runtimes that don’t melt down over time is harder than it looks. “When Graph Runtimes Stay Sane” digs into what actually keeps them stable.

Curious how JAX actually wires gradients, JIT, and vectorization together? This piece breaks down the transformations engine behind JAX’s behavior.

When Missing Files Break Mental Models digs into what happens when your code layout lies to you. If paths don’t match expectations, how far does the damage go?