Technology

So the way things already were?

It's not a case of "seeing the code isn't perfect" but rather, not understanding the myriad problems the code is solving or mitigating.

I'm reminded of this shitshow:

https://en.m.wikipedia.org/wiki/2010_Queensland_Health_payroll_system_implementation

Queensland is a state of about 3m people in Australia. Their health service employs about 100k people. They ended up spending about 900m USD to develop their payroll software and fix the fuck ups it caused.

I'm an accountant by trade, there's a classic "techbro does accounting" style of development we see a lot. Like if you hadn't spent a career learning how complex accounting can be, it would be easy to look at a payroll system and conclude "it's just a database with some rules".

That happens. Even if said new programmer had seen before that IRL the important part of that codebase consists of specific domain area quirks, scarcely documented and understood. They have an advantage in doing something good for the specific stage of that system's evolution, but a huge disadvantage in knowing what the hell it really does.

I'm sure the doge boys are expert grock vibe coders, it will be fine, they've got big ballz on the team, what could possibly go wrong? /s

I did such a thing, but I had a big advantage: the codebase had been done by people who had never really learned to code, and I was a seasoned programmer with 20 years of experience.

Yeah, this is going to end in disaster.

Nah I think it will just be

const benefits = false;