Why rule it all at all?

Some rules for programming

1. If I were you I wouldn't start from 1 at all, at all
   
2. No non-programmers in the environment.
   
3. No less than one failing test to start
4. No more than one change between commits
   
5. No less than one fix per run
   
6. No more than one idea at a time
   
7. Never less than one more bug to be found, ...
   
8. No more than 2 whiskeys for prototyping
   
9. Never drink alcohol before hitting "Send"
   
10. As simple as required. No more, no less.

And one law to rule them all.

Why go boing ?

In the canon of coders' religious wars tab-vs-spaces is one of the greats. Up there with brace-style as an enduring indicator of what coders like to do when there's no code to be written.

So it might be good to see an actual advance in the debate: "elastic tabstops" as proposed by Nick Gravgaard.

Of course this is a guarded welcome, becuase tabs-vs-spaces is a great ol' time-waster, and braces aren't half as interesting (especially since I changed to belts).

Unfortunately Nick reminds me of Arthur Koestler who, in the end of an epic analysis of human pyschology, suggested dumping brain-altering chemicals into drinking water, to fix it. Similarly Nick's solution needs new editors and "code written in this style may be slightly misaligned in older text editors". (Slightly ?)

So - forget about using vi, emacs, Eclipse, ... for code-editing then. But, ar an lámh eile, maybe it is time we did stop using text-editors for code anyway. because "forcing programs into text form causes lots of problems that you might not even be aware of".