Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
The developer who built the foundation of what I work in daily has a bad habit of doing this.
There are many instances where removing the offending property (or even fixing it) has a ton of unforseen consequences. I usually just Mark the property depreciated and move on with my life so I don't try and use it again.
Writing an embedded webserver recycling code that is in use for a few years now. Can't get my ’getStatus.ssi’ working. Turns out ’statusTag’ cannot be used and for the last couple of years noone cared that the status field was empty.
That's the first time I did such a thing and it took me only one unpaid (!) day to debug that piece of crap thinking my idiotic predecessor delivered halfway working code.
Is verifying and communicating broken code really that hard?
undefined
just why?!