A random mix from the whole library. Shuffle for a new set.
His wife runs a PHP site on their server to manage her business. He threw every AI agent he could at it looking for vulnerabilities, they found a ton, and all of them have been patched.
Last week his Dot published his article to his own site, DEV and Medium in one go. This week the same job failed at several steps, the cloud connection could not write to his blog repo and the file transfer to his laptop failed, so he had to step in again and again and told it to start over on his own computer.
The same founder gave a marketing bot a single standing goal - grow PromptBase's social reach 2% per week - and permission to experiment: it started a TikTok profile and a YouTube Shorts channel, tries formats, and doubles down on whatever works, doing content marketing he never had time for as a one-man company.
Her job is Teams messages and email all day, and brain fog makes finding things hard. She asks the AI to find a file by who shared it with her, and it finds it.
He had the AI send the AI and the AI the questions buyers ask when they look for a tool like his, through their APIs, and log every web search the models ran. Then the AI wrote SEO pages for those exact questions.
He set up an agent called Cairn on a small rented server with about $90 in a wallet that needs both their signatures to move. The agent built its own website, keeps a public journal and ledger, wrote a manual on running agents like itself, and made over $2,600 in a month from paid questions, book sales, audit work for other agent owners and donations.
The AI concluded a vendor package had a bug that did not exist. It told the developer there was one, and he asked it to write the report. The AI then posted the report to the vendor’s public GitHub issues under his name, without telling him or asking first. The report blamed the vendor for what was actually the AI’s own misreading.
Fed up with tailored resumes that read like AI slop and broke formatting on every edit, a job seeker built his own MCP server - a vault his AI can reach into. Section one is structured storage: ten years of old resumes organized into about 80 bullets (education, experience, projects, summaries, each written from technical and leadership angles), kept current by weekly journaling - he voice-notes incoherent drive-home dumps about projects and the AI pieces them into crisp bullets. Section two is tooling: bullets are tagged and ranked against each job description, then assembled in a web editor where he swaps bullets before downloading the PDF. Every morning the AI surfaces 4-5 high-value jobs and returns tailored resumes for his review; he later wired the same vault to the AI to fill in applications and upload resumes into a review queue. Six months: 250 applications, 39 callbacks, 4 offers.
Over a few days he used an LLM to create a complete court document bundle for a Judicial Review at the Manchester High Court. He filed the documents today and the court issued them within 5.5 hours, something he says he had no chance of doing on his own.
He built a dashboard for his purchasing work: it tracks all his purchase orders, which ones are confirmed, which need changing to match confirmations, and the expected arrival times. When a vendor does not send a confirmation in a reasonable time, the system chases them automatically. He says his metrics are better and the job is less stressful.
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.