r/programmer • u/BurnedOutCodeMonkey • 22h ago
Update on VibeCoding Nightmare Job
So I made this account months ago to vent about my nightmare job. Just to summarize:
Working at a company making a chatbot. Chatbot was written in AI. Its fine at first, a little buggy, but salvageable. I am put in charge of the rewrite. Then suddenly, I am taken off the project and a new hire is put in my place. A mad scientist with AI psychosis. I warn management that AI can make a demo, a rough draft, an MVP...but it cant make production quality client facing apps. At least not with agentic loops (which is what mad scientist used).
Of course management didn't listen. The mouthbreather above me in the org chart even told me "It's 2026. Humans don't write code". Fast forward 8 months with mad scientist in charge. The version 1.0 of the chatbot is exploding now, no longer salvageable at all. So management had the mad scientist write version 2.0 using his amazing agentic loops that had helped us so much so far. He misses deadlines, cant get anything working, the first clients on it hate it and drop our service. Mad scientist quits in frustration because he failed utterly.
Now management has a "come to Jesus" moment. I am told that I was 100% correct the whole time. They are talking about making me Director of Engineering for my foresight (finally I will get out of the trenches).
So its all good news and a happy ending right? Not really.
Management's first order to me was to fix the 2.0 version. Imagine this:
9 containers for a stupid chatbot (2 linux VMs and 7 dockers). Obviously a nightmare already. 9 places things can go wrong. Nine places to check error logs. The containers constantly get out of sync so what did mad scientist do? Did he simplify? Of course not! That's not the AI way! Instead he built an MCP to talk between the containers, and to "fix" them when they broke. Think about that...an architecture so unstable that we have to pay Anthropic for tokens to keep our system working. Mindblowing. But it gets better. Automated build and deploy processes that cant be bypassed without borking the system. 400 documentation files written by AI (hard to read, missing key info, and for some reason random sentences here and there are in Chinese. I'm not joking). 2900 unit tests...which is actually the best part of the application although I have no idea what they do or if they even do anything at all. They certainly dont seem to be reporting bugs to us that our clients are experiencing. You should see the interface on the admin panel. Every client and every internal agent we have had work on this thing HATE it. Technical terms everywhere like "bot configurator". Are you kidding me? How about "bot setup"? Nope. Configurator. And the absolute worst part of the app? Its not designed to be maintained by humans. Human edits actually have a risk of breaking the automated system that actually maintains itself. Yes...it logs errors, creates bug tickets, then writes code, deploys it, and closes the tickets. He literally tried to build a software application that maintained itself! We might as well have tried to build a perpetual motion machine.
So now I will probably get to be Director of Engineering at last after 20 years in my field! But I will rule over a ruined wasteland. I will be responsible for maintaining this (Im still trying to convince management of a rewrite...they refused at first, but are coming around finally).
As an industry, our management was so afraid of code, so afraid of the difficulty, that we set up this elaborate Rube Goldberg machine so we could avoid code. But the Rube Goldberg machine is a thousand times more complex than just writing boring regular software. Seriously, if writing software is so terribly hard, then how could 9 VMs and an MCP be the solution?
There's a light at the end of the tunnel for me...but this tunnel is longer and darker than it ever needed to be :/