Last Saturday I did a CodeRetreat with Corey Haines at RubyFuza. It was a great and humbling experience. It showed how important it is to continually practise your coding skills. Corey had four important points for better design that I haphazardly wrote down on a scrap of paper. I feel they deserve more respect than that.
Essentially, in order to design better software, we need to write it so that it is easier to change. These points, listed in order of importance, help to achieve that.
I plan to spend the next couple of weeks trying to achieve this when writing code. Do you think these points are in the correct order? Any points that should be added?blog comments powered by Disqus