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
-
With my mere three years of experience, it's already come to strike me equally hard everytime it happens. In the best of scenarios it happens when I want to modify or add something and it dawns upon me that the foundation for it is already laid out. Or when I use some software I've written a long time ago and I use it in some unusual way and go "huh! It predicted this could happen."
Everyone always says the previous developer was crap, sometimes you're right
This is just wrong..
After 10 years maintaining the same codebase, I sometimes find features in the system that I wrote years ago and I forgot they existed, like "Cool, I didn't know the system was able to do that, I completely forgot, I wonder how it works, and God knows how I wrote this shit, let's see..".
I've even found myself starting to implement features that already exist, and then having to revert the changes.
rant
legacy code
my ancient shit