RSS

Tag Archives: development

Avoid Unnecessary Conditional Nesting

Simply put: try to make your conditions as flat as possible.  This makes them generally easier for the humans to parse and understand.  Read the rest of this entry »

 
Leave a comment

Posted by on March 29, 2016 in Coding, practice

 

Tags: , ,

Counting Source Lines

I rarely count the number of lines of source — but here is a quick script to do it. Read the rest of this entry »

 
Leave a comment

Posted by on February 22, 2016 in Coding

 

Tags: , ,

Never leave ‘commented code’ in the source

Comments in code are good. But not when they consist of old code that has been commented out of the live code. Git rid of that. Read the rest of this entry »

 
Leave a comment

Posted by on December 26, 2015 in Coding

 

Tags: ,

Specifying Business Hours

Long ago I worked on a project where we needed to specify the hours that a business was going to be open, and to account for all the various difficulties around holidays and other special days. This is what we came up with and it still stands today. Read the rest of this entry »

 
Leave a comment

Posted by on September 21, 2015 in Coding, Design

 

Tags: , , , , ,

Estimations – the eternal software problem

This post argues “Why We Should Stop Estimating” completely in software projects. It is very problematic. Read the rest of this entry »

 
Leave a comment

Posted by on October 3, 2014 in practice

 

Tags: , ,

Always Test the Software running in the Same Way that Customer will run it

Some programmers have their own favorite ways to run the software they are working on, that is run differently than the way that the customer will run it.  This is evil.  Programmer is not testing what the customer will get, but testing something else.  Is that good enough? Read the rest of this entry »

 
Leave a comment

Posted by on May 14, 2014 in Design, practice

 

Tags: ,

Error Message should be clear, plain, and direct

This post is about a real error message I received and puzzled through.  Luckily, because I was working with open source code, I was able to see a copy of the source, and only then did I understand what the message meant.  An error message should not require you to know and understand the source, in order to understand the message, and I think this is the root of the mistake that many programmers make. Read the rest of this entry »

 
1 Comment

Posted by on August 24, 2013 in Coding, Example Code, Poor Error Msg

 

Tags: , , ,