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
-
@AtuM I think you’ve miss the point a bit here. The issue isn’t about refactoring or undocumented code etc of course we run into that I’m not suggesting I don’t. There in fear of change.
My point is that no one in the years the company has had the app no one has bothered to do any updates to the app whatsoever and just built on top of bad code with no regard for the apps readability or quality. -
@myss ah no matter bud and you can say that again. It was a fight alone just to get them on board with automated testing haha
-
@AtuM it’s a bit of both unfortunately, we have some senior devs but it seems they’ve only started to take notice since me and another dev got hired last year because we’ve started pointing things out and asking why aren’t we doing this? Or why aren’t we doing it this way? Etc. It’s frustrating and we’re the ones cleaning up the mess.
Everyone always says the previous developer was crap, sometimes you're right
This is just wrong..
Working on codebase of a 20+ year old system that the company I work for bought five years ago and in that time there’s been no refactoring, no security updates, no attempt to create automated testing (there is none), new features have just been built on the codebase with no regard for quality and it’s just spun into the horror cesspool that it is today.
I joined one year ago and I’m slowly refactoring the codebase and updating it to get it to a more modern codebase, cleaner code, faster load times and creating a ton of dev documentation so the devs in India can start getting into best practices and start producing quality code.
rant
refactoring nightmare
legacy code
wk266
help me