Published Tick-the-Code Material
Happy Are The Software Engineers.. (article)
My first ever published article is called "Happy Are The Software Engineers.." and it appeared in Better Software magazine in December 2006. The article describes briefly how complete concentration can create the feeling of happiness especially if the task at hand is meaningful. I wanted to highlight that working for software quality is meaningful and with Tick-the-Code you can achieve complete concentration.
Simply put, happiness is Tick-the-Code.
Tick-the-Code Inspection: Theory and Practice (paper)
My first ever scientific paper is called "Tick-the-Code Inspection: Theory and Practice" and it appeared in the peer-reviewed publication of ASQ (American Society for Quality) called Software Quality Professional.
As the name says, the paper reveals all details of Tick-the-Code up to the 24 coding rules. At the moment this paper is the most comprehensive written source for information about Tick-the-Code.
Tick-the-Code Inspection: Empirical Evidence (on Effectiveness) (paper)
My second paper is called Tick-the-Code Inspection: Empirical Evidence (on Effectiveness). It was prepared for, and first presented at, Pacific Northwest Software Quality Conference 2007. The paper presents measurements taken in Tick-the-Code training courses so far (about 50 sessions with over 300 software professionals). The results are revealing. The main point of the paper is that software engineers could keep their software much simpler and avoid making many of the errors software projects are so notorious for.
In the Appendix of the paper, you'll find all the active rules of Tick-the-Code at the time of writing (summer 2007).
Tick-the-Code - traditionally novel technique in the fight against bugs (article)
Pirkanmaan Tietojenkäsittely-yhdistys (Pitky ry) published my article in their member magazine Pitkyn Piiri 1/2008. It is called "Tick-the-Code - uusvanha tekniikka taistelussa bugeja vastaan" and it is only available in Finnish.
Tick-the-Code Inspection: The Book (book, working title)
Since 2006, I'm writing a book on Tick-the-Code to be the most comprehensive written source. I've written first drafts of all chapters, except one. I have received some review comments and acted on them. I have contacted a few publishers and received more comments (no approval yet). O'Reilly editor Andy Oram even mentions us in the Beautiful Code blog. Next, we'll need to get people excited about the concept and the book and then approach the publishers again.
Excerpt from the book
The excerpt changes weekly. Each excerpt is still a draft version and might change before ending in the book.
If the rules in the coding standard are not specific, they won't help. If a rule can be interpreted in multiple ways, it won't be helpful. If the language is too high-level, the usefulness of the coding standard will be very limited. A sentence like
"Dangerous constructs should be avoided as much as possible"
has multiple problems. The term "dangerous constructs" is too vague. Each team member has his own opinion on what is dangerous and what is not. Some of the opinions will match with the coding standard but some won't. The word "should" can be interpreted more or less strictly. The verb "avoid" is clear enough but the end of the sentence messes even that up. The phrase "as much as possible" gives the author a way out. For apparently any reason, he can always use "dangerous constructs". All he needs is a good excuse. This kind of ambiguous, vague, wishy-washy language is not useful in guiding authors in their work or checkers in their checking.
Chapter 2. "Symptoms" goes deep into possible implementations of (code) inspection processes. Here it is assumed that the coding standard is formulated like rules, which is good, as long as the rules are well written. Of course that is what is wrong here. The rules suck. The intention was good, but the implementation doesn't work properly. Tick-the-Code rules are strict and clear.