Welcome!

Welcome to Tick-the-Code.com, the website for practical software quality and the home of Tick-the-Code Inspection. If this is your first visit, take a moment to familiarise yourself with the contents of this site. Further down you'll find the sitemap showing you where everything is. Should you not find what you are looking for, use the Feedback form to let us know. We strive to make Tick-the-Code.com a lively place with frequent updates, so be sure to bookmark us and visit every now and then. You can even contribute directly in the Forum. Have an informative visit and welcome back!	Click the comment for training course details.
PS. Be sure to check the website of our sponsor, www.Qualiteers.com.

Goals

This website is designed with the following four principles in mind. (The principles apply also to source code, which is no coincidence.) Firstly, we want this website to contain all necessary information for its visitors. (Coding rule category: Missing Info) Secondly, there should be nothing irrelevant on these pages. (Coding rule category: Extra Baggage) Thirdly, the structure, layout and usability of the pages should be clear, understandable and easy. Simplicity rules instead of complexity. (Coding rules category: Chaos-Inducers) Fourthly, there should be no risky assumptions on this website, whatever they may be. (Coding rule category: Risky Assumptions) By following these general principles visiting this website should always be an informative and positive experience. Let us know how well we've succeeded in following the principles. You can use the form on the Feedback page.

An Example Rule Introduced

Please, note that using the rules with without proper instructions can lead to misunderstandings. The rules are to be used to uncover unnecessary complexity quickly. The marked rule violations, i.e. the ticks, are helpful hints to the author, nothing more. Contact Qualiteers if you want to know more.

DEAD (WARM-UP) "Avoid unreachable code." Unreachable code is just dead weight. If you find functional looking code in a branch that absolutely can never be executed, mark it. Code that's been commented out also violates this rule. Unless the code is left as a bad example, it should be removed. Outdated code with a comment like '/* This doesn't work anymore */' or unfinished code with a comment like '/* This doesn't work yet */' break this rule, too.

Sitemap