making difficult decisions

As I said in my previous post, I “re-discovered” my original blog.  The last entry in that blog was August 16, 2003.  Wow...almost a year.  It's amazing how much has changed in that year:

At the time of that last post, I mentioned going on a business trip to London, ON.  The trip was cool, EXCEPT for the fact that it was right after the “Big Blackout”.  Anyway, I spent another 7 months on that project before moving on to bigger and better things.  That project was wracked with problems, mainly due to poor project management.  The project was supposed to roll-out on July 1 of this year, but from what I've heard, that isn't gonna happen.

Leaving that project was tough.  I made it through two of the four planned phases before making use of the “at will” clause of the contract.  This gave me the option of leaving at any time for no reason.  In this case, I did give a reason (in fact, I gave several reasons).  Once I informed the client (using the procedure they defined), the project manager decided the most professional way to handle my leaving was to write several flaming emails to me.  He called me several names and informed me I should have just kept my head down and collected my paychecks.  In another breath, he said I should have spoken up about the issues.  anyone see the conflict between those two sentences?

As for the other projects I was working on last year...the 16-bit app is in production and they love it.  Turns out it maybe used for longer than a year.  I've started a couple more projects with that client, so life, in general has been good.

 

Print | posted on Wednesday, May 12, 2004 10:19 AM

Feedback

No comments posted yet.
Title  
Name
Email (never displayed)
Url
Comments   
Please add 5 and 4 and type the answer here: