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

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

Setting Up XnaMobileUnit to run unit tests in Windows Phone 7 XNA Games

Image
Introducing XnaMobileUnit I decided to roll my own unit test framework for Windows Phone 7 XNA games.   I have a couple of reasons why I decided to roll my own.  Among them was the fact that you cannot reference regular .Net assemblies from Windows Mobile Framework.  That means that referencing NUnit was out of the question.  Also using some of the other libraries that can be used for Silverlight Applications didn't quite feel right for me. The framework that I have created, XnaMobileUnit, is very simple to use and provides all the necessary functionality to run unit tests.  I am still working on the framework to provide a few more capabilities and features, but for the most part it is ready to use out of the box.  XnaMobileUnit is open source licensed under the Apache 2.0 License and can be downloaded from http://code.google.com/p/xna-mobile-unit/ .  I recommend downloading the latest source and compiling it then referencing the new DLL. Otherwise you can simply download the l
Read more

Reasons to Stay Away from CSLA

We've been using CSLA - Component-based Scalable Logical Architecture in a product for approximately one year and while it solves quite a few problems it violates some major good practices. No Clear Separation of Layers While at the time that we chose CSLA we knew very little about domain driven design, it is no excuse for the framework to possess the data access layer within the business object. This makes it extremely difficult to separate the concerns. As a result, it is difficult to mock the data-access layer creating many problems when attempting to perform unit tests. This also puts the additional responsibility of data access on the business object class, violating the Single Responsibility Principle( SRP ). Data access layer should be totally separated from the business object period. Having the data access within the within the BO class is not the only additional responsibility placed on the class but is the most significant one I can think of. No Context Validation
Read more