Writing Bug-Free C/D Code

[Sean Kelly]

Knud Soerensen wrote:
> 
> I am working on a set of rules for bug free programing
> and one of them is "Question every line of code" 
> and here the debugger is very useful, it allow you to 
> single step through you code and question everything.
> But you should always do this not only when you get a bug.
>  
> Right now the rules looks like.
> 
> 
>    1. Bug free programing is possible
>    2. Every bug is due to a problem in the programming process
>    3. Question every line of code
>    4. Everything must scale
>    5. Test all code
>    6. Hide your data
>    7. Count your mistakes
>    8. Build it right the first time
>    9. Interfaces are good, but inheritance is bad
>   10. Always leave objects in a valid state

This is a good semi-related article:

http://www.fastcompany.com/online/06/writestuff.html


Sean