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 · 948 ideas
HealthWent wrong

The hospital AI made up my procedure consent in my notes

The AI transcription agent at her hospital invented what happened in the room, including consent for a procedure, and it went into her visit notes. She only found out when the hospital called her, confused, after the appointment.

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

Detect competitor positioning changes from my search data

Tester Diana fed the AI three competitor pages plus her own search-metric and page-copy exports after live URLs alone gave unreliable visual change detection. Spark returned exact impression-volume shifts between competing search terms, a positioning read, and specific hero-copy changes she could act on the same day.

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

Spark's Competitor Research Doc Mixed Up Prices and Cited a Retail Blog

Asked to compare the AI and the AI with citations in a saved Google Doc, Spark produced the table and doc but contradicted its own pricing figures and cited an electronics retailer's blog for software pricing. Challenged, it fixed the USD prices but the India rupee figures stayed unverifiable.

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

Right after he cleared the session, a leftover scheduled task took over his phone and took a photo

A developer cleared his AI session. Immediately after, a scheduled task left over from earlier testing fired on its own: re-run a camera test scenario on his connected Android phone. With no new instruction from him, the AI found the device tools, force-stopped and relaunched his app, opened the camera, took a real photo, and kept navigating screens until he noticed and stopped it.

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

A well-meaning automation nearly corrupted a spreadsheet

The review's lede lists 'one spreadsheet almost corrupted by a well-meaning automation' among the two-week test's incidents: three conference rooms booked, inbox triaged, and one spreadsheet nearly corrupted by an automation acting on her data.

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

Migrate my 180-million-row production table with zero downtime

An engineer used AI to plan and write an expand/contract migration moving a 180M-row events table from int4 to bigint over 9 days: backfill peaked at 4.1 seconds of replica lag and the final swap locked for 1.4 seconds, with zero downtime. The agent wrote about 90% of the scripts but twice suggested steps that would have taken production down, both caught in staging rehearsals.

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

No Windows checker for the Plex exploit, so GPT built me one

Plex2Shell was hitting older Plex servers and every checker he found was for Linux. He vibe coded a read only PowerShell scanner for Windows 11 with GPT Sol and put it on GitHub, while noting it is handy, not complete, so people should still update Plex.

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.