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
-
@gianlu Do you ever have this problem? It's my reasoning for the documentation effort instead of directly working on the project myself...but I don't have too much time to fix my own stupidity in the first place. Rather not write garbage code in the first place, as I'm prone to doing in OOP languages...I tend to take things too far.
-
@OutOfRange Yea but I'm saying it took me a few minutes for code I wrote last week. Took you a few minutes for code half a year ago lmao
-
@mgagemorgan sometimes I look at old finished projects just to see how shitty they are and then realize that I would still write them the same way after years of constantly learning. Not Java, Java is a different thing, I'm still learning new best practices and I constantly change the way I code ending up modifying old code to match my new standards.
Related Rants
every friday
Me: *Uses Spotify in India using VPN*
Friends:
Last year I wrote a sudoku program which did solve easy sudokus but messed up on harder ones. I had got bored after a bit and forgot about it until today I thought I'd rewrite it using new stuff I've learned since and make it work properly.
So I opened it up and look and I'm like 'WHAT!?' because I don't understand what I wrote. After a bit I start to get the idea and see that it was kind of smart even if long and complicated.
If anything, it shows how much my documentation skills have improved.
Now I just have to work out how to redo it in a way I understand.
rant
what?
bad documentation
old code