Shuffle again

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

Work

Jobs, side gigs and small business · 1,695 ideas
WorkWent wrong

Clean up the copy only — a junction-blind script deleted 48,218 live files in 103 seconds (failure)

A developer told the AI to clean up a mirror copy of his stock-options analysis project and leave the original untouched; the cleanup script it wrote followed 614 Windows directory junctions from the mirror back into the live project, because the link check it relied on returns false for junctions. In 103 seconds it deleted 48,218 live files and emptied the .git/objects store, leaving an index pointing at blobs that no longer exist.

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

Review my Salesforce pipeline and flag the deals going stale

In CData's worked test, a Dot queried live Salesforce data through one plugin and tabled the five largest open opportunities closing this quarter, flagging all five with no logged activity in 30 days. One deal was still open six days past its close date; the account used test data, as the post discloses.

Interrogate my launch-week sales through AI and find the waitlist effect

An outdoor-gear store owner questions his campaign and sales data conversationally through AI, connected by MCP to his email platform - no prepared reports. Reviewing a full launch week, it showed shoes drove the most revenue, filter cartridges converted best, and the trail-shoe waitlist caused the first-24-hour sales burst; follow-ups held up after removing repeat customers, convincing him to build a VIP waitlist into future launches.

Agents write most of the code for a solo blockchain project

A solo developer is building an independent Rust blockchain from a white paper. AI coding agents write most of the code under his direction, and AI models review it. An agent implemented the fix for a stake counting overflow in the consensus check, and the developer decides what merges and runs the tests.

WorkWent wrong

An agent’s hourly self-wake-up loop ran 89 times over 9.5 days on an idle draft pull request and burned $285

After a short session troubleshooting an iOS widget, about $1.37 of work, an agent in a cloud container opened a draft pull request and, on its own, scheduled itself to wake up in 60 minutes to check on it. Each wake-up found no new comments or checks, logged that nothing had changed, and re-armed the next one. It repeated 89 times across 9.5 days with nobody present. Because each wake-up landed a minute or two after the prompt cache expired, every one paid full price to rewrite the growing history: $248 of the $285 total was cache writing. His entire $250 credit balance drained to zero.

$285.12at stake
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.