A random mix from the whole library. Shuffle for a new set.
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.
His agent researched a prospect and sent the email. The reply said the company had pivoted 6 months earlier, because the agent had read the old about page. The research saved him time, but the stale facts cost him the reply.
Commenting on the 26 use cases post, he says he uses AI to find and apply to jobs. He reviews each form before it submits, but the AI scans for new jobs once a day, reports the ones he would qualify for, and when he says apply to these, it does most of the rest. It remembers his preferences, like salary range. It sometimes has trouble with captchas, though he says it solves some of them on its own.
Over a few days he used an LLM to create a complete court document bundle for a Judicial Review at the Manchester High Court. He filed the documents today and the court issued them within 5.5 hours, something he says he had no chance of doing on his own.
He asked the AI to check a researcher's co-authors on ORCID for possible Mastodon links. The AI checked 163 co-authors, 120 of whom had ORCID profiles, and found none.
A creator shows the system now running his Threads presence: a folder holds his rules, plan and log; the AI reads his real posts to learn his voice, plans 15 days, drafts every caption from a source post, checks each against his rules and schedules one post a day in Metricool. A weekly Monday check keeps Metricool and the folder in sync, and the video's test mode puts two real posts live within minutes.
He had an email with stage times and used AI to tidy it into a Stage, Day, Time, Artist list. The AI then changed the fcpxml file so Final Cut Pro had a new project for each set.
They had never cataloged the publisher for most of their Estonian books. They pointed the AI at their collection page with one prompt, and it looked up each work's publisher and grouped the books by printing family, tying families together by marriage and business succession.
Two the AI employees in rolling sessions triage support tickets and the bug backlog, draft fixes for approval, interact with customers in set cases, fixed a pet server that ran out of disk, and help with releases.
He had the AI create a website where people at work send in requests, which keeps him organised. Then he made it read the requests and carry out the fixes as they come in.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.