In a diary aside, Manton Reece says his mostly-idle home the AI server automatically updates Micro.blog's 'latest app versions' help page. It checks the currently shipped version and whether an app is in review, while he still writes the release notes by hand.
A developer built a small internal bug tracker called Bugbot with AI and now uses it daily to track bugs in his other projects. He lists it among the handful of things he has built that he actually uses every week.
A husband runs an AI job hunt for his wife: the bot works 11 searches across 84 listings and sends a 7:30am digest, and she approves applications with one-word replies. The search runs daily without either of them opening a job board.
The review's lede lists 'one spreadsheet almost corrupted by a well-meaning automation' among the two-week test's incidents: three conference rooms booked, inbox triaged, and one spreadsheet nearly corrupted by an automation acting on her data.
This only partly worked. Worth knowing before you try it.
He teaches part time at a private school. Lesson plans go in six weeks ahead, and every student now gets a personal differentiation plan, which used to be done per group because per student was not feasible. The Sunday session that took four to six hours now takes fifteen minutes, plus short daily reviews of content and parent comments.
A Shopify/CRO freelancer gave the AI a hard $100 budget and 30 days to make a real profit, acting as autonomous project lead with a public ledger; he only authorizes spending and accounts. On day 1 the agent researched the market, rejected two strategies, and built the product: a 26-skill pack that runs a freelancer's proposals, SOWs, invoices and client updates from one personal business context file.
This only partly worked. Worth knowing before you try it.
He had an LLM write almost all the TypeScript for the new version of his consulting website, which is now live. Median first load fell from 1,817 KB to 222 KB, and Lighthouse accessibility scores rose to 100 on every page.