Let us change our traditional attitude to the construction of programs. Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do. --Donald Knuth

Posts in the programmer's code

Rule #6 - Adapt and Adopt

In 1965, Dr. Richard Feynman won the Nobel Prize in Physics. He was brash, rebellious and rarely passed up an opportunity to point out hypcrisy and irrationality. An experience from his youth can teach us something about programming standards. Continue...

Developer The Programmer's Code

Rule #5 - Code for the Maintainer

Rule #4 - Be Explicit

Should you ever use the var keyword in C#? What about Javascript? Being clear and precise is very important in legal contracts, but it's even more important in software. An unfortunate experience as a teenager helped crystallize the importance of being explicit in both legal matters and software. Continue...

Developer The Programmer's Code C# Javascript

Rule #3 - Never Write the Same Code Twice

Learn how duplicate code can turn your software projects into a circus and what Southwest Airlines can teach us about the benefits of avoiding duplicate code. Finally, Master Po and young Grasshopper bring us a few words of wisdom when it comes to perfectionism and practicality. Continue...

Developer The Programmer's Code

Rule #2 - Fail Fast and Hard

It's counter intuitive, but your programs will have fewer bugs and require less maintenance time if you do less (not more) error handling. Learn how focusing on making your programs fail is the better path toward more stable and more maintainable software. Continue...

Developer The Programmer's Code