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
-
@theScientist mostly trying to make money in college. I didn't have time to do full projects freelance so I started bug fixing. Then as I moved a few years into my career a project that was the most fucked thing you've ever seen came up and the only way company or track could survive was if I just spent my life fixing everything possible. It made me good at catching the bad stuff that most miss.
Also had to read lots of coding standard to perform code review
I started a project at high school 7 years ago, I had no idea what's clean code or design pattern, just learn while keep coding. I eventually stopped because my code is so terrible I cannot understand it anymore.
Now, after 1 year of working, I look back those dirty codes and think it is actually not that bad. Within hours I even fixed a bug with concurrency.
I start to think, instead of learning to how to write good code, maybe I should learn how to read bad code. That's just much more practical.
undefined