elber@dynaum:~/blog$
● posts 35 total

  • Context Is Not a Dev Job

    Half the context an AI needs lives in the heads of the people outside engineering who own intent. AI-DLC only works when that half gets written down, in the same vault and the same spec template the engineers use.

  • Trust the Pipeline

    Every 'we need to ship faster' conversation is actually a 'we do not trust the pipeline' conversation. Five properties of a trusted CI, plus the AI-written Playwright and Testkube setup that gets you there.

  • Your AI Context Belongs to the Team

    Every session with an AI is a teaching session. Most teams throw the teaching away. Here is how to keep it, share it, and let it compound.

  • You Cannot Push a Developer

    Adopting AWS AI-DLC across an engineering org taught me the verb was wrong. You do not push people toward a methodology. You remove the reasons to say no.

  • Frictionless: The Book Behind the Loop

    Nicole Forsgren and Abi Noda wrote the book on removing developer friction. The spec-driven loop from last post is one small, stubborn instance of it.

  • The Spec-Driven Loop: How I Actually Work With an AI

    Brainstorm, spec, plan, implement. Each one a committed document before a line of code. The non-goals section is the highest-leverage thing I write all week.

  • Building a Game with AI Only: How Lanterns Started

    A cozy twilight garden, built spec-first with Claude as the collaborator — and the one decision that changed everything.