Elements of Java Style was an interesting book to read. The book lists code styling conventions for Java and it should be a must-have for any programmers. It contains 108 style rules to follow, which makes your code look standardized and easier to follow for external developers. This book would be really help to start someone off in Java, not requiring new learners to adjust their coding style.
This week’s practice WOD (workout of the day) involved Scribble, repository found in GitHub, where we had to correct any styling errors. For the software engineering class I am currently taking, we followed 108 rules found in Elements of Java Style and additional 19 rules used for this particular class. We were given a custom checkstyle.xml which we used for CheckStyle in IntelliJ. We did a similar practice WOD in class, so I was able to correct all errors within 17 minutes. This time could be reduced if I could find a way to set the custom rules as default for the CheckStyle in IntelliJ.
I personally think this athletic software engineering approach is allowing me to quickly obtain skill sets introduced and master it in relatively quick pace. And the fact that there is a time pressure allows me to work quickly, driving me to improve my results wherever I can.
Honestly, it will take me some time to memorize all the style rules for Java. Without the custom rules provided in xml file, I wouldn’t have been able to finish the WOD in 17 minutes. Maybe one day (very soon, hopefully) I will be able to write a code with 0 styling error.

Prime Directive #3: An external developer can successfully understand and enhance the system