3 ms·
You can buy Clean Code and it's not going to hurt, but I increasingly believe the only way to "step up" is to write code, lots of it. Things like Clean Code ar
by UglyToad 7y ago
You can buy Clean Code and it's not going to hurt, but I increasingly believe the only way to "step up" is to write code, lots of it.
Things like Clean Code are a bit too dogmatic for my tastes now, there are some reasonable ideas there but it's tempting to apply them where they don't fit.
What helped me was starting my own large project [0] based off porting another codebase. I started with wanting to follow Clean Code practices to the letter but now, 2/3 years later and with the benefit of hindsight I'm increasingly moving away from a lot of the Clean Code 'rules' (short methods, etc).
But I also write other short lived projects which allow me to try different things out and learn from my mistakes. When you think how we learn as children a lot is based on making mistakes and I think that is what's missing from a lot of how programming is taught.
[0]: https://github.com/UglyToad/PdfPig https://github.com/UglyToad/PdfPig
- tcbasche 7y agoI find Clean Code hasn't aged well either; a lot of the java-esque design patterns have been superseded with either language features (speaking as a Python/Go developer) or a better overall code architecture / structure. Having said that though, it's a good primer in what's possible in writing clean and testable code.