Tracer Code

Introduction

You aim your gun at a target.   Here are a couple ways you can improve your accuracy.

First, you could research every aspect that comes into play while firing a gun.   These include environmental conditions, specifications of the bullets and the gun, as well of the exact location of the target.   After you do this, you can calculate where you need to position your gun in order to hit the target.

Another way would be to use tracer bullets.   These bullets leave a phosphorus trail from the gun to the place where they hit.   Without all the research needed in the first example, you can get immediate feedback as to where you need to adjust your gun in order to accurately hit the target.

Advantages of Tracer Bullets

• Much easier than laborious calculation
• Immediate feedback
• Operate in same environment as real bullets
• Minimal external effects

If you are starting a new project, "tracer code" may be a solution to pursue.   Just like firing at a target, you face unknowns and environment changes.   Using tracer code will help you get immediate feedback, letting you know if you are on the right track.   Otherwise your time will be spent writing tedious specifications and then crossing your fingers, hoping you come close to the target.

Concepts of Tracer Code

Tracer Code VS Prototyping

Prototype
A prototype is constructed to try out a concept that will help you reach your goal.   It is then thrown away and recoded properly.

Tracer Code
Tracer code is an architectural skeleton on which to hang your code.   It is not disposable like prototypes.   It contains stubbed routines for these things:

• Error checking
• Structuring
• Documentation
• Self-checking

These attributes are not fully functional, but they help you connect your project from end to end.   Once you create this skeleton, you can see how close you are to the target.   Plus, you have just built a lean but complete structure to which you can easily add functionality.

You may not always hit your target, but adjustments are easily made.   It is better to know you aren't close to your target before intense coding begins.   If you only specify and hope for the best, you could realize you have missed the target when you are almost done coding.   Tracer code is much easier to fix than fully-developed code.

Advantages of Tracer Code

• Users get to see something working early
  
  
  • Users will be happy to see the progress you are making.   If you explain your technique, they won't mind the lack of functionality.
  • Users can tell you how close to the target you are BEFORE coding starts.
  
  
• Developers build a structure to work in
  
  
  • This is better than starting with a blank page.
  • Having a skeleton to work with encourages developers, which increases their productivity.
  • Encourages consistency.
  
  
• You have an integration platform
  
  
  • Your system is connected end-to-end.
  • You have your coding environment.
  • You can integrate several times a day and see visible impact.
    This makes debugging and tesing faster and more accurate.
  
  
• You have something to demonstrate
  
  
  • When project sponsors want to see code, you will have code to demo for them.
    
    
• You have a better feel for progress
  
  
  • Cases can be attacked one by one.
    This way it is easier to measure performance and see your progress.
  • Each development is smaller.