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.

An Example Rule Introduced

There are 24 active rules in Tick-the-Code. Each one of them helps to locate either omissions, redundancies, ambiguities, inconsistencies or assumptions in the source code. Individual rule violations might seem minor, but when you let them accumulate long enough, you'll be in trouble.

Marked rule violations are called ticks. Try the following rule on your production-level code and see how many ticks you can find. Then analyze each tick and see if you can't improve the maintainability of your code.

The rule sample changes weekly, so in a mere 24 weeks of diligent visits, you can have yourself the complete set of Tick-the-Code rules. However, there is an easier way and you'll be rewarded with laminated rule cards to top it all up. Get trained! Contact Qualiteers if you want to know more.


"A routine shall do one and only one thing."

A routine should perform its one duty and perform it well. Having one clear task per routine eases also the naming of it.

Operations shouldn't just be put in a routine because they need to be performed in a specific order (procedural cohesion).

A control flag shouldn't be used to select one of the operations in the routine. Acceptable exception: event handlers (logical cohesion).

The operations in a routine must have a clear relationship to each other (coincidental, chaotic cohesion is bad).

Future Work

Tick-the-Code Inspection: The Book (book, working title)

Since 2006, there's a book on Tick-the-Code on the works. Currently the book project is on ice, as I study and gather more material and field experiences to include in the book. The book will be the most comprehensive written source on Tick-the-Code.

Excerpt from the book

The excerpt changes weekly. Each excerpt is still a draft version and might change before ending in the book.

Too many standards

The fact that one coding standard is better than no coding standard at all, doesn't mean that two coding standards or more would be better than just one. As a matter of fact, several simultaneous coding standards have a high risk of being inconsistent. It is also very likely that there will be more than enough rules and guidelines to follow, if you have to observe several coding standards at the same time.

Some companies, especially the larger ones, can have differing coding standards for projects, departments, sites or countries. Sometimes different kinds of software - embedded, office applications, utilities - have differing coding standards. This can cause problems when people move from one kind of group to another and bump into a slight culture shock with their different coding styles. Projects that have to develop different kinds of software at the same time might also be adversely affected by multiple coding standards.

Excerpt is part of Chapter 2. "Symptoms".

Itchin' for a Drive?

Get your bearings:


Click for the sitemap.

Participants comment:

Actual training feedback

Click for training course details.