3 ms·
The hours invested count for NOTHING if the developer doesn't take anyone else with him. Nobody should be a solo developer, especially if they're being paid. I'
by Cthulhu_ 5y ago
The hours invested count for NOTHING if the developer doesn't take anyone else with him. Nobody should be a solo developer, especially if they're being paid. I've had to work with a few prima donna's like that, the one guy basically went offline for six months (and he was the CTO!) to build his "it's full of stars" CQRS framework in C#, then he (and the manager that enabled him) quit and were re-hired as highly paid consultants.
The manager was ousted or toned down a peg later on by a new, more willful manager.
I'll concede that a rewrite CAN improve a software and pull it into the new decade, but it's a big risk, a lot of effort, and a lot of re-discovery - always consider, if that amount of effort and money was invested in the existing codebase, wouldn't it have the same effect?
Another phrase that comes to mind is hype-driven development.
- deepsun 5y agoI knew a prima donna, who went offline for a year. They quit their previous job and were extremely motivated skip salary for 12 months to rewrite a project on a new shiny tech stack. That how the prima donna started my current company. If not for the Magpie, I'd be working somewhere else now.