Chaos Program

At my job we encourage people to use Test Driven Development (TDD). The short explanation of that is that before you write a line of program code, write a test for what it is supposed to do. I confess I don’t always adhere to this. For me the rule would be more like, test early and test often. Testing is a skill and it can be hard. Testing first is also a skill. Like any skill it takes time to learn (and I’m getting better at it all the time!).

For years now, though, I’ve found that even my sloppy and less-than-perfectly skilled approach to testing seems to be too much effort for some people. At a previous job I routinely heard other people complaining that some system/server/software was broken when, in fact, their own code (or configuration or approach or whatever) was really broken. My colleagues and I would say something like, “Did you try it from a different computer?” And, as often as not, when tried on a different computer it worked fine. Reboot and try again. Don’t place blame before you’ve gathered the relevant information. Thank you kindly, call again soon.

See? It’s not just programming. Programming is just an environment where testing is measurable and has well developed tools.

read more »