Slashdot Mirror
Are Unfinished Products Now the Norm?
Paul asks: "Long ago when digital synthesizers first became commonly available, I recall a reviewer lamenting how he was getting more and more products to test whose software was unfinished and buggy and would require updates and fixes (this, before the internet allowed easy downloads, would have meant a journey to a specialist repair center). The review also commented how this common problem with computer software was spreading (this was before Windows 95 was out), and asked if it was going to become the norm. These days it seems ubiquitous, with PDAs, digital cameras, PVRs and all manner of complex goods needing after-market firmware fixes often simply to make them have the features promised in the adverts, let alone add enhancements. Are we seeing this spread beyond computers and computer-based products; jokes apart, will we be booting our cars up and installing flash updates every week to prevent computer viruses getting into the control systems? Can anyone comment on any recent purchases where they've been badly let down by missing features, or are still waiting for promised updates even whilst a new model is now on the shelves? How can we make the manufacturers take better responsibility? Apart from reading every review possible before making a purchase, what strategy do you have, or propose, for not being caught out?"
It's amazing how much effort you can save when you don't take the time to do the job properly. As long as people still buy your product, there's no incentive to actually fix it before it launches.
Software is approaching the complexity of organic life. You know what it means for an organic being to be "finished"?
So what if our software is constantly changing, and is thus "unfinished"? To be finished means it won't improve. Heck, the whole reason for the existence of open source is the "if it's broken, I can fix it" idea.
So, why do we need software to be "finished," anyway?
That depends entirely on perspective. If entropy is seen as a relative process, software that is not being developed is going to suffer entropy as the world around that software is changing. So, in relative terms, there is software entropy.
Hypothetically, if your current 'perfect OS' software no longer has any development being done, when new storage devices or networking devices become available, that 'perfect OS' is no longer perfect. For this reason, all software will always be 'incomplete' in as much as the world around it changes at an ever increasing pace. Some software is outdated by the time that it is ready for launch as a beta product. For more on that, see the big software projects that some groups around the world have attempted, only to find that on launch it is not capable of dealing with recent changes in the world.
All software will always be no better than beta given that the above is true. This means that for businesses, good enough is as good as perfect as that is as close to perfect as it is likely to ever get.
Sure, there are cases where good enough really isn't; medical equipment, space travel equipment etc. but for the vast majority of software for consumers, beta grade is good enough and thus worth releasing.
Fortunately, some companies release beta software/apps and treat them as such by continuing to improve them before pronouncing the software is out of beta stage. When software is released as final product rather than beta, consumers get upset when they find out it's really only beta that they paid for.
But the point is, yes, software suffers from entropy and atrophy is relative terms.
Support NYCountryLawyer RIAA vs People
However, we routinely produce complicated systems that have excellant reliability. For example, glass displays on aircraft - which are quite common in commercial jets. They have to undergo a much more rigorous level of testing before they can be shipped because the liability to the manufacturer is huge. What's the liability if your Sony cam-corder stops working in the middle of your once-in-a-lifetime round-the-world vacaction, all because of a software glitch? The problem is not with the software, the problem rests partially with the people that make and test the systems, but mostly with the people who hire/fire developers, designers and engineers. They do silly things like higher cheaper, but less qualified engineers. They make marketings's brain-fart of the day the top priority. (I realize we're using the world's cheapest 16 bit micro-controller - but could you write the software in Java with a Gui so we can demo at Java One?) And they do things like sacrifice testing to make schedule. And they're also the ones that do things like set budgets and deadlines.
Leave the gun, take the cannoli -- Clemenza, The Godfather
How much does the glass display for an aircraft cost compared to your camera? How much of that cost is testing?
T Money
World Domination with a plastic spoon since 1984
Apart from reading every review possible before making a purchase, what strategy do you have, or propose, for not being caught out?"
Don't buy new products. Seriously, if it is worth buying it will still be on the shelf in six months. Even then I wouldn't buy it until I had read a few *user* reviews, immediately disregarding the top 10%. Check out some forums. Unofficial forums that is, publishers are notorious for nuking negative comments. I do not trust professional reviews. Ever. Even for existing software things can be pretty sketchy for a while. Consider how often Apple manages to botch iTunes, and that's their billion dollar baby. I know it's not what you wanted to hear, but you have to do your due diligence and be patient.
Frankly I don't see this problem going away until it is legislated away. If the bills concerning paid advertisements (i.e. the Sony PSP blog et.al.) have any teeth and clear consumer friendly rules, then reviews might have some value again. Not a lot, but some. Beyond that, liability is the only thing that's going to reign publishers in.
Platform advocacy is like choosing a favorite severely developmentally disabled child.
I'd argue the opposite -- Theres no such thing as a finished product.
Of course there is, even in the software industry. Consider the software that runs the Voyager probes. It was completed 100% and shipped.
The issue is not that it's impossible to finish something, it's that 80% done is where the money is. Companies that go overboard on quality either go out of business or get relegated to serving a niche market. Quality is expensive and customers will repeatedly drop their cash on unfinished products that pass the dog and pony show.
In the UK, if a product is advertised with certain features and those features either do not exist or do not work, you can return it for a full refund under the Sale of Goods Act. Items must be "fit for purpose" and advertising must be accurate.
That really is the best stratergy. If companies get too many returns, they will realise that their products are not up to scratch and either go out of business or fix them.
BTW, don't be fooled by retailers who claim you can't return things once the packaging is opened. The law appilies to everything, even software and things sold in those stupid "blister" packs you have to destroy to open. Just because the manufacturer made it impossible to find the defect without opening the product doesn't mean you can't return it. Even cars, which loose thousands of pounds in value when you drive them away from the dealers fall under the same law.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC