A time tested methodology for handling complexity....

I am reminded of this every so often.  Usually after getting spun around for awhile but not adhering to these time tested principles of dealing with complexity.  Call it problem solving 101.  Call it the programmers creed.  Call it what you want.

So what is this time tested nugget of wisdom?  Morsel of goodness, wisdom of Solomon.

Build a little - test a little.

That's it.  Really

Ok - I will extrapolate just a little.

Problem solving is a iterative process.  Systematic and predictable.  If you are not rock solid with something, then just add a little and test it.  Do NOT add a lot and NOT test it, because then, when you finally do get around to testing, you will have a much wider spectrum of error to content with. 

The minimalist approach.  Build something in its simplest form, get it to behave as expected and then add a little more to it.  Do NOT add a bunch of stuff up front and then compile it or run it later.  No. 

build a little - test a little.

Embrace the minimalist approach.

Finally, learn now to use the debugging tools in the environment you are working.  Be able to evaluate variables during run time of your program.

The end