Before any blame is implied, let’s look at the reality of the situation. Maintaining separate development and test environments on production equipment takes a ton of time and effort to not only stand-up, but also to maintain and keep in sync with your production systems. Getting resources from IT and QA is fraught with challenges, the least of which is pointing fingers when systems crash and users blow up at you.

So, what is a busy administrator like you to do? If you are reading this, wouldn’t you rather spend time testing and working with some of the cool new tools like PowerPivot in SharePoint 2010 for example, rather than struggling to install them? Excel Services is like the Maple Bacon of enterprise software – it’s sweet and sizzles and you KNOW you want it. 

So AIIM Community, when was the last time you forgot to test things before you put them in production?

Add a Comment

You need to log in to post messages. Click here to login.

Comments

test the bacon?

Submitted by Randy Moeller January 11, 2012 - 3:29 PM

HaHaHaHa. Great one. SobSobSob. True one. More true if the risk is lower. Systems that follow heavy regulations do a darn nice job. But or other systems I've had IT folks tell me their boss said it moves to production tonight regardless of the errors as tomorrow is launch date so fix it as the tickets come in. Sigh.

I wonder if there are any copyright issues with the cartoon...........

Report

Was this helpful? Yes No

Reply

Subject  

Comment