</> htmx ~ Working With AI: A Concrete Example
In this essay, Carson Gross walks through a concrete bug fix in hyperscript to show where AI helped, where it fell short, and why keeping a knowledgeable human in the loop is what kept complexity in check.
Carson Gross June 29, 2026 I am, generally, ambivalent towards AI. There is no doubt it has become a very powerful tool for development in the last year, but it also comes with many dangers, both for us individually (e.g. the slow dulling of our intellects) as well as collectively (e.g. environmental concerns, increasingly expensive personal computing, etc.) In “Code is Cheap(er)”, I warn about The Sorcerer’s Apprentice problem, where a developer becomes reliant on AI and is unable to understand and properly address issues that come up in the systems they are building. In this article I…
saved by
related reading
- Cleaning up after AI rockstar developers - Jesse Skinnercodingwithjesse.com
- After Automation | Everyevery.to
- AI Horseless Carriages | koomen.devkoomen.dev
- How AI assistance impacts the formation of coding skills \ Anthropicanthropic.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Danger, AI Scientist, Danger - by Zvi Mowshowitzthezvi.substack.com
- Effective harnesses for long-running agents \ Anthropicanthropic.com
- Why AI-Generated Code Becomes Hard to Maintain and How to Fix Itnewline.co
- Would you fly on an AI-coded plane | Hackle's bloghacklewayne.com
- Harness design for long-running application developmentanthropic.com
- Current AIs seem pretty misaligned to meblog.redwoodresearch.org
- Ralph Wiggum as a "software engineer"ghuntley.com