3 ms·
I had lunch this week with some former coworkers. When I'd started working with them it was on the 20 year old C++ engine that ran everything. Even at that ti
by nineplay 2y ago
I had lunch this week with some former coworkers.
When I'd started working with them it was on the 20 year old C++ engine that ran everything.
Even at that time there was large team 'rewriting' it in Java. That team was dissolved about 2 years later.
During the course of my employment two more large teams were spun up to do a rewrite and then came crashing down after a year or two.
I hadn't seen my coworkers for about 7 years. Naturally they were still working on the C++ code. Naturally they'd seen two more rewrite teams come and go while I'd been gone.
I'm not sure why I'm bringing this up......
- iKlsR 2y agoIsn't it customary for new hires or teams to drop into a legacy codebase and within weeks propose a rewrite.
- akmarinov 2y agoYeah but now the AI can do it! /s
- palmotea 2y ago> Isn't it customary for new hires or teams to drop into a legacy codebase and within weeks propose a rewrite. And if they're actually serious and not just venting, it's also customary calibrate downward how much you trust their judgements.
- _DeadFred_ 2y agoYes but did the subject matter experts have the kind of trust/working relationship those at the SSA have with DOGE? That should smooth out this project.
- ttyprintk 2y agoIn medium-sized companies, I learned not to represent anything as rewriting. Some projects were massively reshaped, sure.