One thing I would like to start doing more often would be to try implementing the boy scout rule in my code submissions. After reading chapter 1 of Robert Martin’s “Clean Code: A Handbook of Agile Software Craftsmanship,” I don’t know why, but I never really implemented this rule as much as I should when I would create my code submissions. “Change one variable name for the better, break up one function that’s a little too large, eliminate one small bit of duplication, clean up one composite if statement”(Martin, 2008). I would like to try this out in the future and hopefully become a better coder and engineer by doing so.

One thing I would want to avoid doing would be writing more comments than needed in my code submissions. I always struggled with writing less comments on my code submissions and looking back at what I’ve done, I can understand why I need to write less words and more code. Most of my code submissions are extremely crowded and hard to read because of my comments and I hope that I can stop this habit once and for all in the future.

While reading chapter 3 of Martin Fowler’s “Refactoring: Improving the Design of Existing Code,” I learned that “comments are used as deodorant”(Fowler, 2018). Meaning, that more comments in a code submission means that the code is bad and is either hard to read or it doesn’t run/work. It’s best to get rid of unnecessary comments and to use the extract and rename methods in order to write and or keep necessary comments.

References:

https://thixalongmy.haugiang.gov.vn/media/1175/clean_code.pdf

http://silab.fon.bg.ac.rs/wp-content/uploads/2016/10/Refactoring-Improving-the-Design-of-Existing-Code-Addison-Wesley-Professional-1999.pdf