Tuesday, November 14, 2006

Test-driven writing of standards

We all know about test-driven development, and even test-driven management (which proves to be just setting goals and checking them at the end of the year).

Now I introduce Test-Driven Writing of Standards. Indeed you can start writing coding standards, but it is likely you will miss something, so when you see another ugliness in your code you need first to go and check if your standards cover the problem. If not you need to add it to the standards, and then raise a defect based on the newly added coding standard.