Proactive versus reactive code testing
An often overlooked, but extremely valuable skill when writing code is testing that code. The larger and more complex a developer’s codebase, the more likely it is that things will go wrong or break down. To ensure a small bug doesn’t have a ripple effect that takes down a whole system, good software developers learn to test their code early and often.
Writing effective tests is a skill in its own right. At Code Platoon we teach students to practice Test Driven Development (TDD). TDD is a methodology that anticipates and reduces the likelihood of bugs by proactively coding tests around a desired function before designing and implementing that function.
The tests tell the software developer what the function should not do so that their initial attempt at writing the code which supports that function is clean and less prone to rework. It is a common practice throughout the tech world, but it cannot be taken for granted!
Seeing code through the eyes of others
Developers write lots of code, for sure, but they also spend an enormous amount of time working with code written by someone else.
Before diving into a new codebase from another coder, a developer must first understand how its components interact to achieve the desired result. The ability to do so requires a level of patience, knowledge of predefined constructs, and pattern recognition that does not factor into autonomous code writing.