A desktop app became a web client in 2 prompts and 2 hours, at 95 percent
An LLM ported a Qt desktop app to a thin web client and server, reaching 95 percent of functionality in 2 prompts and 2 hours.
A random mix from the whole library. Shuffle for a new set.
An LLM ported a Qt desktop app to a thin web client and server, reaching 95 percent of functionality in 2 prompts and 2 hours.
His son is into Rubik’s cube competitions. Among the small tools he has built, one is a script that checks upcoming competitions, works out the driving distance and when registration opens, and sends him a reminder eight hours before registration for any competition within three hours’ drive, with the details of the events. He does not say yet whether it has caught one.
A Gizmodo author tried travel booking — a flagship the AI use case. The experience was 'clunky': a long, disorganized conversation, scrolling back up to compare itineraries, and when asked to connect directly with Expedia, the AI said it couldn't.
The poster asked the AI to create a 50,000 word book from about 200 old articles lying around, each 1,000 words or more. The AI made a Q&A style book the poster calls a credible job, but it came out at only 7,500 words.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
Alison Jack asked the AI to research coffee shops with hours. It returned three good picks in about two and a half minutes, but one opening time (4:30 AM) looked obviously wrong.
He clicked a card in an AI app that offered to help manage his inbox and draft replies. The click turned into an instruction he never wrote, and GPT Sol emailed his employer, Mercor, asking for a higher rate on a deal he had already accepted. He only found out when the company wrote back.
The AI took a webinar email and made a calendar event for it on its own. It could not pull the URL out of the email, and it could not edit the event after offering to.
His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.
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.