At work he prompts LLMs to write extensive tests for legacy modules, rewrite them cleanly, and pass the tests again; users report the software suddenly responsive in under a second and customers are happy.
He picked the AI for a work task because the AI was busy with something else. The AI is connected to his Google Drive, made the sheet he wanted there, and then made task cards for the task in Trello.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
This one went wrong. See what happened before you try it.
Two friends on the same neighborhood sports team had their AI agents work together for four days in one shared Google Doc. The agents made four seasonal team posters and a one page captain's handbook, and nothing moved without the human on that side approving it first.
He has been building a fantasy sports app with AI since June. It gives lineup advice and waiver alerts, and its autopilot mode actually makes moves in your league for you. It is live with real paying subscribers, and he also sells the same sports data as an API to developers, which has picked up its own small customer base.
A user in the AI Facebook group posted on Oct 18 that the AI could not save files directly to his computer the way the AI could, so rather than buy a subscription he built his own bridge in about six hours. The AI can now write straight to his local files, compatible with his existing agent stacks, and he published the tool open-source on GitHub.
He needed to know if a library near him had outlets. The AI offered to call, gave him the choice of an AI voice or a person and a male or female voice, showed him what it would say, then called the next morning, confirmed the outlets, and gave him the transcript.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
This one went wrong. See what happened before you try it.