He merged five scattered file messes into one, then the AI and an LLM wiki in Obsidian reviewed and cataloged everything. He says knowing what is in it and how to get it back matters more than tidy storage.
He wanted to digitize his papers. The AI worked out how to use his feed scanner, and for about two hours he sat feeding pages in while the AI ran the scanner and catalogued the documents. He could talk to it through a conference speaker and watch it work in VS Code.
His Ubiquiti access points are full of firmware bugs. Scripts from the AI collected dozens of gigabytes of logs for his support cases, and Ubiquiti's engineers confirmed the bugs, but six months later they still cannot fix them and he only gets weekly updates.
This only partly worked. Worth knowing before you try it.
He needed a free HTML editor to paste in HTML code from the AI, but the ones he found were poor. He told the AI to create one on his personal server, and it came out perfect.
The AI wrote the tooling to annotate historic map tiles and a CV model ran across the rest for an exhaustive study of unlisted formal gardens in Ireland; a decade-planned project done in a weekend.
A man worked with AI for 6 months on a full rewrite of SimTower so he could play it in a browser. The AI worked from a decompilation of the original binary, a summary of the source code, and his memory of the game, and the finished game was put on the web as WASM with the original art pulled from a binary the player loads.
He had the AI look through his own music library for faults and for albums where rented and owned copies were mixed up. The AI made a full interactive view of what it found.
Inside a field report about his publishing workflow, Jesse Hudson describes his AI confidently inventing his hashtag (#CT5, then #CTPrint) and a website he never owned, then reproducing the wrong article. Only after he made it search did it find his real site, CTEFight.com, and the correct hashtag.
This one went wrong. See what happened before you try it.