Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
It's common story everywhere. Managers who gave impossible deadline. Programmers who can't help but write shitty codes to meet the impossible deadline.
I'm currently in the role of "next dev" and have taken over probably one of the worst PHP legacy projects.
What bothers me the most is that the original company, which "developped" this complete mess, didn't bother, during the 8+ years they were "maintaining" it, to inform the customer of a well needed refactoring or upgrade.
Imagine a company where the CEO just sucks his customers dry over years by maintaining something that wasn't even maintainable since the start.
We apparently paid 6 figures per year to these fucktards and the thing got so bad it should have been replaced 4 fucking years ago...
What a complete asshole of a company.
@PonySlaystation 8 years can be a pretty good span for a codebase. Value for money maybe. pains me to say it but even with slow development due to horrid legacy code it can still be cheaper than major overhauls. I've worked in projects which have spent a lot of time on code quality and future proofing maintenance only to see the entire code bare scrapped and replaced within 3 years ( due to changes in api, preferred language or similar) which I personally loved... but as we calculated the cost for those restarts it was significantly more than the one ancient legacy repo we have.
but of course - if you compound the costs of all devs leaving agree forced to work in a legacy crap repo it changes.mm