When Development and Production Collide

Following my previous post, I recently ran into some other problems. My current job puts me in the development side of the fence. Having worn the hat of a consultant and implementation delivery person, I know how new projects can be tough. However, while I was still in my development process, Production decided to run some tests. As a result, some of my data got corrupted. This week, as the release date draws near, everyone, including Production, is looking to me for delivery. What I don't understand is why is it that when Production breaks my work, I have to be the one fixing it? I guess because I am the author, they can easily push the responsibility back to me. I'm the one that didn't do it right in the first place.

If that's the case, why is it that everyone tells me that I am not doing anything wrong?

Pilot Versus Production

Recently, I was put on a "Pilot" project at work. Over the years, I've always been one that can adapt to new technology. This time around, I guess the pain has outgrown the gain. Working in pilot mode with production data at a production schedule is not the thing to do. If I was the one administering this pilot with a customer, I believe the sale would not have gone through. Maybe I have been too good of a customer.

Tell me it's not my aging that's making my pilot program so difficult.

Microsoft Word 2007 Crashing On Exit

For a little while now, my Word has been acting up. Today, I got fed up, and did a bit of searching. Came across this article describing a similar situation. The fix listed totally fixed my problem.

Word 2007 mystery crash resolved