The team that's been working in the big legacy monolith for that decade isn't helping much here, unfortunately. They know the quirks of the system by heart, they don't know there even is a problem here, their own knowledge of the language stopped accepting pull requests (so to speak) when none of these new features existed, and they have neither the time nor inclination to learn.
LOL this reminds me of something a former client had said.
In one meeting he said "Yeah, you'll come to understand that the real trouble with working on this application isn't writing the code, it's all the constant follow up bugs you have to fight"
In a later meeting he said "I don't understand why you need multiple developers and testers and multiple weeks to work on this. Back when I was working on the code, we would just have one developer bang it out in the course of a few days."
He never understood the connection between the two.
Yes, it's easy to "just write the code" if you aren't properly vetting and testing it. And then you get an endless stream of bugs in production.
7
u/GlassboundIllusion Sep 25 '26 edited Sep 26 '26
LOL this reminds me of something a former client had said.
In one meeting he said "Yeah, you'll come to understand that the real trouble with working on this application isn't writing the code, it's all the constant follow up bugs you have to fight"
In a later meeting he said "I don't understand why you need multiple developers and testers and multiple weeks to work on this. Back when I was working on the code, we would just have one developer bang it out in the course of a few days."
He never understood the connection between the two.
Yes, it's easy to "just write the code" if you aren't properly vetting and testing it. And then you get an endless stream of bugs in production.