Monthly Archives: August 2012

Waste: Asking Whether to Fix a Bug

Some parts of our development are outsourced to another company, and the people in charge in our company like to be in control, so they have requested that the outsource company confirm everything they do.  This additional bureaucracy causes a tremendous overhead, where often the effort needed to approve the work, is more than the work itself.  This is  a source of waste that should be eliminated. Read the rest of this entry »

Leave a comment

Posted by on August 23, 2012 in Coding, practice


Tags: , , ,

Not all Bugs Deserve the Same Handling

It is good to put in place standards for handling reported problem, but the process is not the same for all bugs.  Some deserve careful elaborate process, while others should just be snuffed and move on. Read the rest of this entry »

Leave a comment

Posted by on August 21, 2012 in Coding, practice


Tags: , ,

#30 Avoid Session Variable Abuse

When programming an application to run in a web server or app server, there is often the need to retain a value from interaction to interaction.  It is easy, and very temping, to create a new session variable at the moment, and store a value there, and retrieve it at a different point in the interaction.  It is an easy solution, that causes a large maintenance problem, this post explains why. Read the rest of this entry »

Leave a comment

Posted by on August 17, 2012 in Coding, Design


Tags: , ,

Write Documentation, not Legal Contracts

I recently encountered an effort where a customer had decided to use some unanticipated web page functionality that conflicted with the working of the product.  There was no way to rewrite the product to allow that exact customer modification.  The result was to write a warning in the manual, but the warning chosen was not very helpful. Read the rest of this entry »

1 Comment

Posted by on August 13, 2012 in Design