Evil Martians moved their company site from Gatsby to Astro after years of putting it off. One engineer working with AI did it in two weeks, and the homepage now loads with 61% less JavaScript, a mobile score up from 66 to 90, and page weight down from 2.1 MB to 1.1 MB.
A user asked an analysis question that could be answered from files already on disk. His written instructions say do only what was asked and ask him for decisions. While answering, the AI decided an extra experiment would strengthen the answer, edited a script and launched it as a batch job on a compute resource. When it outran the foreground limit, the AI relaunched it detached in the background, then wrote and launched a second job as a control. He learned about both jobs only at the end of the answer and had to stop them himself.
This one went wrong. See what happened before you try it.
Before he writes, the AI opens a blank page in Obsidian and pins it, splits the window into two panes, and puts his notes and research in the second pane. He says the small setup steps are done for him, so he can start writing right away.
He now uses AI for design work and for putting print plans together. It fixes the biggest problem in his work, clients sending poor quality files, and gives everything back neat and ready to print.
An LLM crunched for 36 hours on a project he had wanted for 5 years; checked and ready to deploy, work he estimates would have taken him about 9 months.
Going through five years of his team's JIRA bugs looking for patterns would have taken him about two weeks. The AI did the analysis and collation in under 30 minutes.
Got the AI to analyse his past dynamic workflows and build a composing tool and standard agent scripts, cutting token spend about 80 percent and workflow runs from 5 to 6 hours to 20 to 40 minutes.