Right. so this is the deal. Break open a bottle of Cursor AI. Get Speech to Text working. If you are Irish, quantity has a quality of it's own. Tell the AI to make you a viral app. When it won't compile, yell at it util it does. At some point it will randomly destroy the codebase. Version control my rear end, scream at it until it compiles. You will probably have about 6 lines of code though, and it won[t actually do anything. Repeat ... Until you have 100 lines of code that will compile.
Copy that into notepad. Make it clear to the AI that you know where it lives.
Then copy/paste that Notepad masterpiece back into Cursor and whisper softly: “Behave.”
The AI will respond by hallucinating 4000 warnings about semicolons. Ignore them. They’re lies.
Don’t fight it. Let the madness flow.
When you finally get something that vaguely resembles an app screen — a rectangle with colors, maybe a rogue text label that says “Hello from 1998” — take a screenshot. Congratulations. You now have App Store marketing material.
Deploy to internal testing. Watch as your friends can’t install it because of certificate hell. Curse loudly, threaten the AI with re-training, then try again. By the fifteenth build, you’ll have something that doesn’t crash until at least the splash screen. This is called “progress.”
Rage coding isn’t about making good software. It’s about establishing dominance over silicon. Every time the compiler gives you an error, you treat it like a duel.
Repeat this loop until you’ve cobbled together 200 lines of unstable genius. Then — and only then — submit it to the store with a title like “AI Rage Builder 3000.”
It will be rejected instantly, but that’s not the point. The point is: the machine knows you’re serious now.
