You Can't Handle the Truth!


"You can't handle the truth!" is an all time favorite movie line by Colonel Jessup, played by Jack Nicholson, in the movie A Few Good Men. In the movie Lieutenant Kaffee, played by Tom Cruise, is trying to get Colonel Jessup to admit ordering a "Code Red".  Kaffee is demanding the truth to which Jack Nicholson's character replies "You can't handle the truth". Col Jessup goes on to explain that he is the one that has to make the difficult daily choices to protect the very freedom that Lt. Kaffee enjoys but chooses to question the method on.  Life is like that sometimes.  We are afraid to tell the truth; to be honest.  For many different reasons we refrain from being honest. This apprehension is necessary in many cases to avoid being rude or unpleasant.  Yet other times, it may be necessary to be unpleasant because the truth is not only important but necessary and obligatory.  Providing estimates and level of efforts in software development is one such case.

In software development the fate of the delivery depends on the programmer. It's the programmer that must provide working software. If the software has defects, the programmer will need to fix them at the eleventh hour.  Level of effort is normally provided by the programmer.  Much of the program's estimates and resources are gathered and allocated based on the programmer's estimates. That's a great deal of responsibility for the programmer.

The programmer, being an overachiever by nature, wants to shine and deliver the product correctly and quickly. Or maybe, it's because the programmer is naive that he underestimates the effort.  For those reasons programmers tend to provide underestimated levels of effort.  Sometimes it is not even and underestimation but simply that the programmer wants to provide a pleasant answer.  Providing the project or program manager with one day level of effort is a more comfortable message to deliver than a two week estimate.  Telling the customer that the server will require 30 minutes of downtime is more pleasant than telling them that it will take four hours.

As comfortable as it may be to provide pleasant estimates, it is better to provide the realistic estimates. Or if you really don't know it's better to say let me look into it and get you an estimate.  The true level of effort will reveal itself sooner or later. It is better to reveal it sooner rather than later.  Not only can managers and customers handle the truth, they deserve it.  As much as they hate to hear the unpleasant truth, they subconsciously demand it. The manager deserves to know the true estimate so they can make the appropriate decisions, raise the red flags, acquire the additional resources.  These decisions adjustments are easier to implement sooner rather than later. Time is money and the longer you delay revealing the true estimate, the more that the solution is going to cost.

Programmers must stop self imposing short deadlines in favor of pleasant responses. In either case you will deliver the bad news. If you self impose a tighter deadline you will eventually have to deliver the bad news that you underestimated the level of effort. Then, how pleasant will be when you tell your manager that you have not completed your task because you underestimated the level of effort or even worse how pleasant will it be when the project fails?

Comments

Post a Comment

Popular posts from this blog

Simple Example of Using Pipes with C#

Image
So I decided to dig into understanding how Asp.net works under the hood, out of curiosity.  In the articles that I found the authors described the architecture in lower level details.  One of the things that caught my eyes was the use of named Pipes as a means of inter-process communications by the architecture.   So I decided to dig into that portion a little bit deeper.  I discovered that the .Net framework has a namespace for named pipes and it's quite easy to use. I intend to demonstrate a small example that I cooked up rather quickly by setting up a named pipe server and then connecting a pipe client to it.  Before I do that, I want to say as a disclaimer that I don't know that this example demonstrates the best way to use pipes.  What it does do is show the most straightforward way to use them.  Also, before you use pipes you should consider using something else like WCF instead if you need well defined interfaces, as using pipes is pretty raw.   Being the type of perso
Read more

Putting Files on the Rackspace File Cloud

Recently, I’ve been playing around with Asp.Net MVC and I (along with some friends) am creating an Asp.Net MVC application that can access files from our website. This means that files must display on the site as well as provide a way to download/upload them. I won’t give away all the details of the project but I will say this: Sharing photos is one of the driving forces for our project.  The files are only image type files( jpg, etc) The files must be uploaded by the users and stored somewhere within our system.  We don’t necessarily know at this time how much storage space we need but we think that we will need a little at first but possibly a lot more down the road. This means that the storage of these files must be scalable. The uploading of files must be controlled by our system.  Right off the bat we started our application and were uploading files to the web server with no problem.  We only did it this way to kind of prove our system model. We were just basically writing
Read more

Why I Hate Regular Expressions

I have a love-hate relationship with regular expressions.  I admire their power yet I hate the pain and agony they have caused on more than one occasion. Just recently one of my colleagues used a regular expression for validating passwords. It seems pretty fair to use regular expressions for validating character sequence patterns. After all it seems they were created exactly for that.  However when regular expressions fail they fail hard.  What I mean by that is that they usually fail in the production environment. In case you are wondering what a regular expression is take a look at the wikipedia explanation of regular expressions . So we go live and all of a sudden new users can't be created because the regular expression says that the password is not valid due to one of the complexity rules.  But how?  The regular expression passed all the unit tests.  In fact the application works fine in our development and test deployment.  So what happened? The validation works fine unti
Read more