|
They should provide warranties as long as they can test the code in the expected environment - For example, a programmer who wrote a firmware for one type of hardware should offer a warranty.
Web Developers for example may offer a warranty, too - But only in the environment they have tested the App in (Otherwise we'd have hamsters keeping CP Netscape Navigator-compatible).
You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, the tallest guy in the NBA is Chinese, the Swiss hold the America's Cup, France is accusing the U.S. of arrogance, Germany doesn't want to go to war, and the three most powerful men in America are named "Bush", "Dick", and "Colon."
|
|
|
|
|
Bostik have the right idea. They say they have no control over how the user uses their product. Software is a bit like glue in that respect.
I may not last forever but the mess I leave behind certainly will.
|
|
|
|
|
Why Software Developers should offer code warranty. As long as they meet the requirement, why they be questioned. Off course any pure software development should go the whole processing of SDLC[^]. Other than this why they be liable for their code. When they deliver the product someone(project manager/product manager along with the stake holders approved it. This is the way it goes IMHO.
Please leave the Coders
|
|
|
|
|
Developers should offer warranties, for a price. This should encourage better code from the developer because they understand they will be required to fix the code. The warranty should only cover the fixing of the code and not be liable for its use in an unknown/untested environment.
|
|
|
|
|
Yes a warrantee is a good idea. it also helps define bug vs desired feature and opinion.
The company I work for offers a 1 year warranty.
Any bugs after a year they may still fix, but its a painless way to not have to say if they wanted a feature they should have asked for it a year ago.
|
|
|
|
|
...holding a company directly financially liable for a buggy product is (IMHO) the only sure-fire way to ensure that management gives due importance to the effort required to properly build and test software. Software products often tend to be rushed out the door in order to meet the requirement that the company establish market share early. And all too often, this happens at the expense of quality.
/ravi
|
|
|
|
|
Amen. The only reason most software out there is of such poor quality is that no-one is liable for it.
|
|
|
|
|
It's sad fact that "release now, fix later" has become the mantra for many early stage companies. I've actually heard managers deferring stability and feature completeness to V2 and V3 because (and I quote), "Nobody takes V1.0 seriously."
On the flip side, you have Google, where robust products remain in Beta for an extended period of time because nobody's holding a gun to their head.
/ravi
|
|
|
|
|
If a customer wants warranties, they must pay more. They must accept the fact that considerable time and efforts will be devoted to "useless" things like writing tests, refactorings etc.
Quality and warranties don't appear out of thin air. They are the result of hard work. And money, obviously.
“Today is the first day of the rest of your life.”
|
|
|
|
|
Athari wrote: considerable time and efforts will be devoted to "useless" things like writing tests
You don't test code?
|
|
|
|
|
I agree. We do offer a warranty for our software, and we also tests the software in many ways (we have a Beta Tester), but going deeply with unit testings and others will definitely change the delivery time. In my experience no real bugs but instead customers that want to change some screens and also the logic ... this seems to be minor but it introduced others bugs, and this is very annoying.
|
|
|
|
|
Let's face it: software is the only industry apart from medicine where nobody expects perfection (or even "actually works") and doesn't complain if they don't get it. Or indeed are even willing to pay again for the same experience!
Why? Why should we have a "special status" and "the right" to sell shoddy goods? If a car manufacturer makes a lemon, it's their fault, and their cost to repair. If the tin of beans you buy contains a mouse, they get sued.
How can we be expected to be taken seriously as a profession if we allow ourselves to release cr@p? Yes, I know, you don't have time. Yes, I know, management won't let you do it properly. So perhaps we need legislation to allow us to have a change of attitude: if management get charged each time we release buggy code, perhaps they will start listening and letting us improve the way things are done.
That and it might scare some of the absolute retards out of our "profession" - and if you don't think there are any, then I'm sorry - but you are in that group. See here: http://www.codeproject.com/feature/weirdandwonderful.aspx[^]
The only instant messaging I do involves my middle finger.
|
|
|
|
|
/ravi
|
|
|
|
|
OriginalGriff wrote: Let's face it: software is the only industry apart from medicine or law where nobody expects perfection (or even "actually works") and doesn't complain if they don't get it. Or indeed are even willing to pay again for the same experience!
FTFY.
|
|
|
|
|
I had forgotten the legal industry.
Gawd knows I try hard enough to forget it!
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
Would you buy a car that was built off of the requirements that developers normally get?
I say the answer is "it depends".
Solid, known requirements, priced to support SDLC, then I'm inclined to give a yes opinion.
Otherwise, no.
Real life involves trade offs and equilibriums (of millions of software developers),
and the market has settled on the current state of affairs.
If customers could get warranties/guarantees for the same price,
they surely would demand it. Or they could offer developers a premium
for warrantees in the current environment.
But the defacto supply/demand has led to lower priced software (get it done!)
and the absense of guarantees (usually). So it really doesn't matter what I say/want.
|
|
|
|
|
"The difference between genius and stupidity is that genius has its limits" - Albert Einstein
He clearly anticipated the computer age and the infestation of mindless evil colloquially referred to as "users".
Now - on the other hand, some sort of warranty should be given about the quality of advice and frustration level occurred when the "help desk" is outsourced.
Note to Virgin Mobile: Die! Die! Die!
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
there are too many parameters at play.
what if the code is running on an unintended platform? do we ever get to end of life the code? how was the code being used?
in general yes you should be responsible for your code but you are also responsible for running a business as well.
you want something inspirational??
|
|
|
|
|
I agree. There are way too many variables in that equation.
"If you feel the urge to add complexity, just go home early. You ain't gonna need it." - YAGNI
|
|
|
|
|
A previous employer was very responsive to our customers. When something broke, we were on it ASAP. However, because we were so good at fixing stuff, some customers would blame problems on our software just for tech support help. Tech support would explain what the issue was with other software when they could. Occasionally we made a code fix to work around their environment.
While its good customer service, that amount of support has the possibility to break the bank. This is what service/maintenance contracts are for.
Hogan
|
|
|
|
|
Why should the kind and amount of support or liability be restricted by law?
It's up to the developer to offer a cheap product with bad support or an expensive product with a lot of support or support as an add-on etc.
If the product is not worth its money, the client should simply not buy it or complain about this and ask for another deal.
If the software is for free, why should there be any warranty?
So, generally speaking, NO, warranties should not be enforced by law. Whether it is fortunate for the developer to provide warranties, should be up to the developer.
|
|
|
|
|
Customers should undergo acceptance testing, once they sign the code off as "doing the job" then there should be no further requirement to maintain that code - not without additional cost anyway.
The reason is that there are so many factors that could change and break the code, many of which can be unknown during development. If customers want to ensure they are covered for those events then they can sign up for a support contract!
NOTE: I am looking at this from the point of view of bespoke development. I might take a different approach to some off-the-shelf product
There is nothing to see here, move along
|
|
|
|
|
There is no guarantee of how the code will be structured underneath as that can be counter productive.
But the customer should receive a piece of code that does the job they specified and paid for. This does therefore not cover any change external to the code that then breaks it i.e. changing infrastructure, windows versions, DB schema, etc.
You wouldn't accept it if you bought a car, tv, fridge etc that had a production flaw. Code is no different.
|
|
|
|
|
I agree 100% with AJ. Being both a developer and salesman of software products, part of the written agreement with the customers, was that it executed as advertised.
|
|
|
|
|
Code is very different because it is dynamic and running on top of a variable and changing environment, whereas a TV is static and only based on a few standardized connections (power supply, HDMI and some other standard A/V inputs and outputs). It's the same for your other samples.
Who decides where the base problem is located? Who is the one analyzing the problem? If I am the one who has to analyze it, who is paying me for analyzing a problem that is maybe caused by the user itself, by Microsoft or some external libraries (e.g. Developer Express)? What if it's not my fault? Does the user has to pay me if he broke my application? Is Microsoft in charge and has to pay me so I can pay the user because the forced upgrade to .NET 4.5 broke my .NET 4.0 application? What if the user installed .NET 4.5 using the automatic update function of Windows? His fault? Microsoft's fault? My fault?
Even if it is my fault, what is a valid solution and who decides if it is valid? What if my solution is a workaround which the user does not accept or the administrator don't want to apply because of some kind of paranoia?
There are too many questions, too many parameters, too many pseudo computer scientists (a.k.a. users).
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
