A builder runs AI as a night shift for his side project. Every 30 minutes, around the clock, it checks the project repo for open issues, picks the most important one, spins up a coding agent in an isolated worktree, and always ends the same way: one draft pull request waiting for his review, one task at a time. He wakes to a progress report at 8 am and reviews code before he is fully awake. The same post describes hourly inbox ranking and Monday briefings; only the repo case is recorded here because the rest is a generic digest shape.
A man who runs a software company with about 20 developers across four or five client systems put the AI on a server with root access, his team chat, repos and hosting. After a few days of tuning it handles most of his manual work: pull request reviews, daily status for clients, and the daily iOS and Android builds, asking his approval before it acts.
GitHub Classroom shut down on August 28, and his Cloud Code Academy ran on it. He wrote a PRD first, then rebuilt the platform with AI over the weekend, with a template repo, feedback pull requests, autograder webhooks and an instructor queue, in 25 commits.
He moved his reading history from Goodreads to BookHive, onto his own AT Protocol data, and pulled in Audible data too. The AI cleaned up 389 books along the way.
He built an invoice processor for a small law firm: PDFs arrive by email, get read with OCR, matched line by line to case codes, and pushed into the billing system. Anything it is unsure about goes to a manual review queue with a screenshot, and months of edge cases like 8s read as 3s went into its rules.
He runs a five level system where the AI Design makes his Instagram carousels, from a basic prompt up to a full design system with AI generated images and a looping video cover. The first carousel made this way reached 4,500 views with 89 saves.