News for hackers. Stuff that matters.
Re:Mistakes engineers make in large established codebases by cratermoon on Wednesday January 08, 2025 @12:51PM (#42636652)
If the schedule is three years, and in the meantime the product being rewritten isn't getting maintenance, the company might as well go ahead and fold and save everyone pain and disappointment. https://www.joelonsoftware.com/2000/04/06/things-you-should-...
Re:Mistakes engineers make in large established codebases by simoncion on Wednesday January 08, 2025 @08:38PM (#42640642)
If the product is not getting needed maintenance, then yeah, maybe.

But, man, sometimes software is fit-for-purpose and can really be just be left alone for extended periods. Other times, the users of that software upgrade on a hemi-annual or annual schedule (or even LESS frequently), so they'd never notice a three month delay in new releases.

Re:Mistakes engineers make in large established codebases by cratermoon on Friday January 10, 2025 @11:26AM (#42657072)
> sometimes software is fit-for-purpose and can really be just be left alone for extended periods

I suppose if the software maker is a functional monopoly in that space and the customers are cursed withe vendor lock-in, sure. I can think of Major Software companies that barely maintain their products yet companies stick with the garbage because what choice do they have?

Re:Mistakes engineers make in large established codebases by simoncion on Friday January 10, 2025 @04:06PM (#42660237)
> I suppose if the software maker is a functional monopoly in that space and the customers are cursed withe vendor lock-in, sure.

Given this statement, it might surprise you to learn that there are folks who aren't keen on software development for its own sake, and really rather dislike having to re-learn how to use their tools when they those tools get significantly change with no clear benefit to those users.

See also: the folks who are perfectly happily using "ancient" versions of -say- Photoshop, or WordPerfect, or Word or...