Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 970 ideas
WorkPartly worked

He rebuilt a dead online exhibit and put it back at its old address

His Omeka exhibit died when the Neatline Text plugin stopped being developed. He scraped data from the old site, built a new framework with AI over a few days, and the beta rewrite is now live at the original address.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

The AI built a full GoHighLevel system while the owner was in meetings

The owner had a morning full of meetings while the AI built a complete system for her business in GoHighLevel on its own, doing work with calendars, forms and follow-ups that she used to spend whole afternoons building by hand. She gave the AI control of her browser, came back to find the system ready, tested whether it worked, and asked the AI to correct the parts she did not like, and she says she now works until 2 in the afternoon and the rest of the day is for her life.

This only partly worked. Worth knowing before you try it.
HomeWent wrong

The AI replaced Assistant and my smart plugs barely work now

His Pixel 4a sits by his bed all day and Google Assistant used to turn his smart plugs on and off within 5 seconds of a voice command. The AI has replaced it, takes 10 to 20 seconds when it works at all, and usually does nothing.

This one went wrong. See what happened before you try it.
WorkPartly worked

Find why my 90-night booking priced below breakeven and counter at $7,450

Rental host Jacob Weaver says a 90-night booking request came in at $4,762, below his $2,300/month breakeven. Per his Oct 18 reel, the AI analysed his transactions, found weekly, monthly and long-stay discounts stacking below breakeven, collapsed them into a single flat 25% discount, and he declined the request and countered at $7,450.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

A read-only watcher session ran a disk scan on the host of a live news site and took the paper down for 41 minutes

A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.

This one went wrong. See what happened before you try it.
HobbiesPartly worked

The AI found the records I needed for my Canadian citizenship papers

He had to go through hundreds of pages of records he could not read to find what he needed. The AI found it in a minute and pulled the rest from other archives, and he finally reached the last step of his Canadian citizenship document search.

This only partly worked. Worth knowing before you try it.
Show 10 more

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.