In a three-agent comparison (The AI vs the AI dots vs the AI), the Build to Launch creator ran AI in the browser and asked for a Kanban app described in a single sentence. The app rendered and worked: cards could be added and edited.
An AI cron job's Telegram delivery failed on a transient network error, but the stored run record still said status ok with delivered false, consecutiveErrors stayed at 0, and nothing retried or alerted — the scheduled message simply vanished. The failure was only visible by digging into the run diagnostics; anyone watching the chat or the job's status saw a healthy run.
This one went wrong. See what happened before you try it.
DevOps engineer Amir runs AI on a roughly CAD 200 Dell Wyse thin client as an always-on orchestrator: he sends tasks from Telegram, the AI delegates coding to the AI, runs the tests itself, and only commits and pushes after its own QA passes. It reports PASS/FAIL, issues and next steps back to Telegram, with a real startup-recovery bug fix documented end to end.
Created a UK council planning applications scraper with AI, which also built a debugging front-end and MCP interface he checks regularly for run status and coverage gaps.
At 11 p.m., a teacher's the AI built her a complete print-ready activity packet for the novel her class is reading — answer key included. It also sends her a daily morning briefing drawn from her calendar and email.
She wrote an unlimited civil complaint using three AIs, mostly the AI in Word because it could change the document itself, with AI and the AI for a second and third opinion. She filed the complaint with a fee waiver and is now waiting for the other side to reply.
A hobbyist says the AI assembled the firmware running his living-room lights and fans: an ESP32 web server driving a radio transmitter. It also built him a Streamlit app to explore the signals, and the code is public on GitHub.
A video summary was made for others to use in their teaching. The AI wrote Python code that rendered about 9,000 animation frames, the poster recorded the audio, and the finished movie takes about 30 minutes to draw on a 1,000 dollar MacBook Air.
His new Kasa bulbs would not talk to Home Assistant, and the problem had sat open for eight months. With the AI talking directly to the devices, they now work, a fix he says he could never have written or fixed on his own.