Identifying Problems that Already Have A Historical Lessons Learned

Recently I ran into a problem that I had I had solved before.   This time the solution was being implemented by another developer. As it turns out, he ran into the same traps that I fell into when I solved that problem.  The only problem is that I was not able to identify all the pitfalls before hand.   

How did I fail to identify the traps and pitfalls?  I had been there before, but I failed to pass along these lessons learned.  My danger antenna never went up.

What lead me to buy into the his solution and eat a big piece of the gullible cake was  three things:

  •  Being under extreme pressure to a meet deadline
  •  Believing in the confidence of this very capable programmer "Oh it's easy, I got it, I will have in a couple of hours"
  •  The alternative solution was many times harder so this seemed to be a silver bullet

In the end then solution worked but it was many times more effort than the programmer assured me.  And much of that has to do with being my fault.

I am dissapointed in myself because I did not ask my self what lessons I had learned previously and then therefore did not pass the information on.

So what do you do to when faced with a challenge to ask yourself "Have I been here before?" and if the answer is yes, how do go about identifying the lessons learned in order to pass them on?

Just something to think about.  I am interested in hearing your answer to this question.

Comments

Domepeace said…
I guess that would put you in a difficult spot. I know that the mantra can be to "Trust your programmers." But it's not always so cut and dry when a deadline looms. I wish I had the answer. Maybe there is no concrete answer. Maybe you handled it the best way based upon the circumstances.
September 28, 2011 at 6:41 AM
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