Post

The codebase that I deal with at work was entirely vibecoded by my boss and it's such a hulking piece of shit it's utterly mindbending. One like = one horror story

Last week, I approved someone for an account on our website. That approval request took about 30 seconds; I discovered that was because it somehow triggered a flow to mutate *literally every single record on the entire website*

I just fixed an issue today where the page listing whether our invoices had been fulfilled took 51 seconds (!!!) to load because it was doing an n^2 operation on every single bill in the company site

My boss often forgets which features he's implemented and will randomly start using different words to describe the same concept. The AI won't make the connection, so it gets built twice. We had Hours, Shifts, Schedules, and Work Offers, which all did the *exact same thing*

When he talked about hiring me, I asked him what framework he was using; he said he didn't know. When I asked him what language he was using, he said " I know there's JavaScript"; I said Django probably would've been better. He immediately put Claude on ultracode and ported the whole thing

I found out we have something like 4,500 columns in our database, most of which are worthless, duplicates, or not read by anything. Our table for Work Orders has over 120 columns

At one point I found out that staging *and production* were completely down because my boss's signature move, telling Claude "merge all outstanding pull requests", merged in work that wasn't done. He does this so often I no longer open PRs unless I'm certain they're done

We had something like 16,000 tests in the project. I eventually asked Claude to remove some of them because we were adding a couple hundred every week (two person project btw)

According to Claude, * 10,781 tests covered no unique lines * 3,403 tests were fully redundant * 1,900 covered only hard-coded frontend wording * 300 literally could not fail * 90 literally just tested Django fixtures

My boss also had an LLM hooked up to help ingest emails as work orders and auto-generate summaries. One page on the website ran those LLMs *every single time you loaded the page* instead of just caching the results (you may notice this is a common theme)

So, one part of the site stored money in cents; later on, another page would take that float and divide it by 100. However, *other pages also did the same conversion*, so $250 became $2.50. This happened for both accounts payable and accounts receivable

My boss does not understand what git is and refuses to learn. He asked me to assign a pull request to a new hire, later merged it accidentally ("merge all outstanding pull requests"), and asked me to un-merge it so it would stay assigned. I realized he thought pull requests were tickets

Check out the y-axis 😃

One cutover we had to do ended up discovering that program-wide, we had about 15,000 lines of dead API being exposed to the internet. This had all accumulated after maybe what, 3 months?

After we switched from JavaScript (Node.js, apparently) to Django server-side rendering, my boss got mad that some flowchart UI element didn't look *exactly* how it looked previously and demanded that Claude reimplement all the Node rendering logic site-wide. This happened I think twice