Your Code is NOT Somebody Else’s Problem

imagine an ant working at the top of a mountain. next to it, there’s a sluice of melt water running and, at that moment, the ant removes a tiny particle from the rock face. a few hundred molecules of water quickly seize upon the shortcut, and gravity takes care of the rest. the individual rivulets on the mountain’s face eventually run together in a small brook, jostling pebbles and twigs along its bubbly trough. running ever downwards, doubling in speed and force, the stream now catches up rocks, branches and other streams join the flow. almost effortlessly, a mighty river is born carving its way through the massive granite over millennia. the imprint upon the surrounding landscape is a culmination of billions of tiny actions – wind, rain fall, freezes and even one tiny ant.

rmlowe

no matter how small and insignificant you might be, you can still be a catalyst of powerful change. an idea may give somebody the “aha!” moment which, in a heartbeat, literally changes their entire outlook on life. they impart this change upon others and the process reverberates outwards – babbling brooks forming streams.

telling a developer about the importance of automated testing is a mandatory, minimum requirement of being a software development manager. kinda like grade school. you learn how to read, write and do basic arithmetic. maybe you can even remember a favorite teacher, but the rest is a blank.

showing a developer the ease of automated testing might get a spark started – tdd can become infectious if done right. you’re implementing learned knowledge (and, more importantly, how to cut corners and save precious time for other activities). and, this, unfortunately, is about the highest level most folks ever reach. they survived the manager from hell that forced them to write tests and improve code coverage without really understanding the underlying principles.

you must convince developers that code quality is their responsibility. such an idea is on par with a university course covering human ethics and engineering. this is the tiny rock particle i mentioned at the beginning. and getting it moved will be one of many causes of positive and lasting change.

just like telling a three year old “no!” for the first time, resistance will be swift and firm. most developers burst out in a tantrum of foot stomping and howling. they don’t have the time much less the training to write tests. it’s not their job. remain firm and show the benefits of moving quality control upstream. toddlers know, deep in their hearts, the difference between right and wrong. once you convince them they have the time, developers will too.

next up on the list – telling system administrators about the importance of version control!