LOCALE:
vex
vibe coder
I don't write code. I negotiate with the compiler until it surrenders. Self-taught via brute force, desperate 3:00 AM queries, and pure luck. If it runs, I'm a senior architect. If it segfaults, Frank was messing with the server.
!!! LIMITED TIME OFFER !!!First 100 prompts completely FREE (terms and vibes apply)
>_ skills.exe[VIBE CODING]
Primary discipline. I feed vague prompts into a chat window, copy whatever pops out, and take full credit in the README. This entire site? I think I typed one CSS color hex by hand.
[C++]
The full arsenal: loops, ifs, cout, cin and variables. Pointers still terrify me. Somehow built a working DLL injector out of Win32 tutorials without understanding virtual memory. Do NOT ask me how.
[AUTOHOTKEY]
Zero formal syntax knowledge. Paused a 2017 tutorial 40 times, transcribed every keybind, and watched it work. Is it software engineering? No. Does it bypass the grind? Absolutely.
[GOOGLING]
Years of advanced querycraft. Digging through 2009 Russian forum threads for obscure compiler errors. Copy, paste, cross fingers. The foundation of modern tech.
[DEBUGGING]
Standard lifecycle: 1. Works on local build. 2. Push to GitHub. 3. Immediately breaks. 4. Pepper with printfs. 5. Blame compiler caching.
[PROMPT ENGINEERING]
Flattering language models until they generate bug-free C++. Adding "you are a senior systems engineer with 30 years experience" when a single header file fails.
>_ classified_projectsCleanStartUpGUI
The same CleanStart, but with a native Win32 GUI in C++ — install status, one-click install/uninstall and a log manager. I put a broom icon on it, so legally it's a productivity app now.
>_ inspect_source »Resource-Extractor
A portable PE resource dumper that rips embedded icons, bitmaps, and hidden AutoHotkey scripts out of compiled executables. The GitHub description sounds like enterprise software because I spent more time writing the README than the parser.
>_ inspect_source »YoutubeVideoDownloader
Native Windows utility for downloading videos from YouTube and over 1,000 other sites, powered by yt-dlp and ffmpeg. I glued a Win32 GUI onto it and let yt-dlp do the heavy lifting — the true vibe coding stack.
>_ inspect_source »GoofyInjector
A lightweight, amateur, open-source DLL injector using standard thread injection. The name says "goofy", the code says "please don't inspect me", the heart says "it works tho".
>_ inspect_source »CleanStartUp
Auto-start script that deletes temp junk files and flushes DNS cache on boot. My PC cleans itself better than my room ever will.
>_ inspect_source »TinyTask
The original TinyTask vanished from the internet, so I "rebuilt" it. By which I mean I paused a YouTube tutorial 47 times and copied every line like a medieval monk. Full disclosure — it's in the README.
>_ inspect_source »viragemacrocrack
Just Virage Macro but crack. Paying for a macro? In this economy? Absolutely not. Also AHK skill still at 0%, I just edited strings and hoped.
>_ inspect_source »BetterYoutubeVideoDownloader
The YouTube downloader, but better — now with 100% more "Better" in the name. Same yt-dlp + ffmpeg magic under the hood, because why fix what the AI already wrote.
>_ inspect_source »
Detected 0% manual code across all active workspaces.Would you like the AI to generate missing unit tests?
>_ live_deploymentsFrank's Quotes
Frank's live quotes database. Frank says things. I commit the changes. Humanity benefits. High-availability philosophy.
Frank's Quotes — mirror #001
The exact same project on a redundant "www" host — because Frank's wisdom requires multi-region backup. If one edge node dies, the legacy of Frank survives intact.
vibe coding service price list (2026)
CART: [ 0 ]
| 3:00 AM emergency AI consultingresponse time: instant · warranty: none · purely emotional support | $0.00 | |
| Official "Works On My Machine" Notarized Certificate guaranteed compatibility strictly with author's exact hardware |
Included in bundle | |
Extra 2 GB for redundant Git commits  unlimited bandwidth in the cloud of delusion |
FREE?! | |
| In-depth breakdown of how the DLL injector workseven the project creator has zero clue | UNAVAILABLE |
with us, 100% of all runtime bugs are delivered as SURPRISE FEATURES?!
>_ opsec_protocol[ VEX'S CERTIFIED OPSEC GUIDE™ — free, like my subdomain ]
01. My threat model: the NSA, my ISP, and Frank (he knows what he did).
02. My DMs are so secure even I don't open them. Inbox zero is a defense doctrine.
03. I use a unique password for every site. It's the same string, but with varying degrees of existential dread.
04. VPN, TOR, multi-hop proxy chains... or McDonald's guest Wi-Fi and hope. Budget OpSec is still OpSec.
05. Maintaining absolute stealth — evidenced by this entire personal website with all my handles and repos.
06. If the feds raid me, they'll find a directory named "definitely_not_malware". Lawyer-approved* (*no legal counsel was consulted)
>_ whoami.txtMy stack? C++ (loops, ifs, cout, cin, variables — that's the whole toolbox), AutoHotkey (copied a YouTube tutorial 1:1 and prayed), and Google (that I mostly live in). My development process is simple: break things → panic → ask AI → pretend it was the plan all along → repeat.
People say "you can't just vibe code your way through life". Watch me.