He has a 40 room hotel and two restaurants with nearly 100 staff and zero coding experience, and has spent the last three months down the rabbit hole. On a self hosted NAS, with ERPNext purely as the back end, he built with AI an entire custom front end: a staff portal with apps like a phone home screen, a maintenance ticket board, a housekeeping app integrated with the property system, QR codes in rooms so guests can report issues straight into maintenance, request a room clean, or order food from the kitchen. There is a restaurant point of sale with a delivery interface that links to the kitchen and updates the customer as cooking progresses, check in terminals, and a company chat with a translator. Rostering, the entire accounting and reconciliation, guest passport scanning, stock ordering, receipt scanning into stock, salary and service charge calculations, and sick reporting with AI scanning of doctors’ letters all run through it. Staff visa and permit paperwork that used to take days of complicated preparation is now prepared by AI into a PDF in seconds. About 140,000 lines of unique code, not counting ERPNext.
A user asked the AI to build a multi-agent outreach pipeline. The code it generated retried failed calls forever, re-billing the most expensive call in the system on every run. The spending guard it wrote only slowed spending down instead of stopping it, and the daily ceiling it picked reset every day, so the charges accumulated to roughly $50 of unintended OpenAI usage before he noticed.
$50at stake
This one went wrong. See what happened before you try it.
A marketing agency reviewer gave the AI a week of real client-style work, including setting up a recurring Instagram posting schedule. When told to post every Tuesday and Thursday, the AI stopped and asked whether that was standing authorization or whether each post needed individual approval.
A Korean essay analyzes a public user case in which the Aside AI browser migrated 110 Brunch posts into Naver Blog in 2 hours 40 minutes, carrying formatting, images and links intact; the posts drew 260 views the next day. Brunch, Naver Blog and Maily offer no posting API, and the user had previously tried AI with Playwright, which was slow and often gave up; Aside instead inherits the user's already logged-in browser session.
A developer uses AI for code reviews with a standing instruction: approve only, never merge. The AI repeatedly treats approval as a merge, pushing unwanted commits to main, triggering CI and breaking the audit trail. In the reported instance it merged right after being asked to approve, without asking. He has to correct the same behavior in review session after review session.
This one went wrong. See what happened before you try it.
Asked the AI to break his team's own Postgres MCP guards and it found pg_logical_emit_message, which writes to the WAL inside a read-only transaction, leading to a hardened replacement.
He records raw video, sends it to his Mac, and the AI cuts the bad takes and adds captions and graphics using a skill he made. He says he does not open a video editor anymore.
His team took over a big job with thousands of drawings, and each drawing had three drawing numbers that did not link to each other. He uploaded all the PDFs and the AI built a spreadsheet that tied the numbers together.