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.
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.
CALL
"Call subroutines where feasible."
Modularity is based on routines and methods. There are several valid reasons to create a routine: to hide details, to isolate or reduce complexity, to introduce abstraction, to avoid duplicate code, to simplify complicated boolean expressions, to limit effects of change to name but a few.
Remember that length adds complexity, so short sequences of code make good candidates for routines.
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.
In your work, you need to answer the question "why do we want to do quality?" with a resounding "because I can, and quality is good for me." In other words, you need to have a reason for quality. Nobody can give you this, your attitude towards quality is yours alone. Everybody can tell you whatever they will, and they can monitor and control you all they want, but if you are not committed to creating good quality, you'll produce the opposite the first moment you're left alone.
If you think that creating testable and maintainable source code is meaningless, you probably won't bother. If you see no reason to spend a little extra time in making sure your code is as clean and clear as it possibly could be, you'll leave it as soon as it seems to work or passes all its tests. If you don't have the drive to aim higher than the norm, you'll create code that is harder to integrate, more difficult to test, clumsier to extend than it could be. If you lack motivation, you'll inadvertently make your code unnecessarily complex. If you don't care, who will?
You need to care about what you and your colleagues produce. It mustn't be irrelevant to you if your code breaks in testing, or if a customer finds failures in it. You, as well as all your colleagues, must strive for quality. You must decide that's what you want, and you're on the right track. If you then have the necessary capabilities and enough time, you're close to success.
The conclusion of Chapter 3. "Root Causes" is that there are exactly four ultimate reasons for failure in software. One of them is lack of motivation.
Get your bearings:
Click for the sitemap.
Participants comment:
Click for training course details.
