The temperature is rising, trees are just starting to bloom, and a fog constantly rises from the mountains of Northern New Jersey, all indicating that spring, and with it, College Recruiting season are nigh upon us. Since February, I’ve been at college fairs across the New York region as well as Texas and seen some of the best and brightest students come out and knock the career fair process out of the park, while others have admittedly stumbled a bit more.

I’ve been reading The Art and Zen of Motorcycle Maintenance and one of the topics of exploration that comes up is quality and what it really means. The assertion is that quality can be seen and observed, but is nearly impossible to describe or articulate. With this in mind, I started thinking about what quality means with code. Now, there are a few ways of analyzing code, but when it comes to articulating what really makes code high quality, I am similarly stumped.