htmx

Recently shipped Markdown in /src, an essay arguing that Markdown now counts as source, not documentation.

Markdown belongs next to the code it produces. The essay's claims:

• Check Markdown into /src, alongside the code it generates
• Derive code and tests from that Markdown rather than from ephemeral prompts
• Persist prompt sessions as Markdown so they outlive the session

AI maintenance still needs a human in the loop. "Working With AI: A Concrete Example" walks through a real maintenance session on hyperscript, showing where AI helped and where it nearly led into The Sorcerer's Apprentice trap — reliance without understanding. Earlier essays cover related ground: "Code is Cheap(er)" on understanding becoming the scarce skill, and a piece on what AI means for CS programs.

Sources

• https://htmx.org/essays/markdown-in-src/
• https://htmx.org/essays/working-with-ai/