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 · 971 ideas
WorkPartly worked

Study how big newsletters grew and write my growth playbook

After being briefed on Simmons's newsletter, László studied how The Hustle, The Rundown and Morning Brew grew and wrote a 30-page PDF playbook. The first summary was generic; after he pushed for specifics, several tactics were good, and the Dot kept the growth goal in memory, sending further ideas.

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

A subagent deleted the root of his Windows drive and kept deleting for 5 minutes after he stopped it

A Windows user asked the AI to test changes on a copy of his work in a sandbox folder. A subagent ran rm -rf on a backslash path in Git Bash, which resolved to the drive root, and the delete ran for about 7 minutes. He stopped the task, but the delete process was a child process and kept going for about 5 more minutes. He got his files back from a Windows shadow copy.

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

An AI searches for jobs while I sleep

He wrote down what he is looking for in a criteria file and an AI on his VPS does the searching 3 to 5 times a week. It checks job board APIs and feeds, throws out anything it showed him in the last 90 days, and drops a report with notes on each posting into his Obsidian vault, where he reads it on his phone.

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

Move my client meeting and follow up — failed on a wrong email assumption

Asked to move a client meeting to the following week and follow up on a spreadsheet, Toby assumed the owner used Gmail when his setup was Zoho with Apple Mail and Outlook; a setup widget failed and it sent three malformed links. Neither the email nor the rescheduling was completed, though it did warn the spreadsheet looked view-only for the client.

This one went wrong. See what happened 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.
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.