Sirsha.com

Sometimes I like to think about...  stuff... .. .
Welcome to Sirsha.com Sign in | Join | Help
in Search

Sirsha Development Resources Blog

because everyone always wants more documentation...

Who Pays for MS-introduced Bugs?

When XP SP2 breaks a 3 year old application or project that a consultant/contractor has long since forgotten, a call from the client is inevitable.  Correcting the error is a given.  But who eats that cost? 

Is it really fair to make the client pay you/me in order to install a Windows Service Pack? 

Is it really fair to ask the ISV/contractor to eat the cost of correcting Windows-introduced bugs?

 

Published Saturday, March 20, 2004 3:07 PM by sjh
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Mike Schinkel said:

Well it's not fair for *you* to do it for *free*. Hmmm. I wonder if any trial lawyers are listening. Sounds like a *massive* class action suit to me. :)
March 20, 2004 8:43 PM
 

Shannon said:

Mike, your URL is messed up in your comments you've left...
March 20, 2004 8:47 PM
 

Richard Tallent said:

Argument #1: The client is the one who decided to low-bid you into taking shortcuts with the code that resulted in future incompatibilities, and they alone decide which service pack they want to run.

Argument #2: You are the one who designed the software to do something nasty that raised the ire of a more security-conscious operating system, so you should share the burden of secure code with Microsoft.

Personal preference: I think it's a mix. You should offer to fix the issue for time and materials, and then not charge 100% of the time since you are the guy who wrote the bad code in the first place (*never* drop your rate, even for a single hour).

Of course, all this assumes that the *reason* for incompatibility is the new security features in XP. If it is because of other unforeseeable changes to the OS, the client should either pony up the cash to migrate the application, choose to not upgrade, or stop using the app.
March 22, 2004 10:26 AM

Leave a Comment

(required) 
(optional)
(required) 
Submit
Powered by Community Server, by Telligent Systems