Motivation of software professionals
in [Java Programming]
|
From: Leif Roar Moldskred on 12 Feb 2010 14:37 In comp.lang.java.programmer Brian <coal(a)mailvault.com> wrote: > > You clipped what I wrote about revealing known problems. Yes, because that doesn't really matter when it comes to legal liability. Well, that's not entirely true -- if someone can prove that you _did_ know about a flaw in the product, you're going to be in hot waters. But merely showing that you were ignorant of a flaw isn't sufficent to absolve you of liability: the cook in the soup kitchen isn't going to _know_ that the food he serves is contaminated with salmonella and Toyota didn't _know_ that their accelerator pedals were faulty. It's not whether you're aware of flaws in your work that matters, but whether you did your job properly and with due diligence. A cook who serves salmonella-infested food because the salad he'd bought had been contaminated at its point of origin is not liable, but the cook does so because he's failed to follow basic standards of hygiene and kitchen procedure _is_. -- Leif Roar Moldskred
From: Brian on 12 Feb 2010 15:44 On Feb 12, 1:37 pm, Leif Roar Moldskred <le...(a)huldreheim.homelinux.org> wrote: > In comp.lang.java.programmer Brian <c...(a)mailvault.com> wrote: > > > > > You clipped what I wrote about revealing known problems. > > Yes, because that doesn't really matter when it comes to > legal liability. > > Well, that's not entirely true -- if someone can prove that > you _did_ know about a flaw in the product, you're going to > be in hot waters. But merely showing that you were ignorant > of a flaw isn't sufficent to absolve you of liability: the > cook in the soup kitchen isn't going to _know_ that the food > he serves is contaminated with salmonella and Toyota didn't > _know_ that their accelerator pedals were faulty. > > It's not whether you're aware of flaws in your work that > matters, but whether you did your job properly and with > due diligence. That is true in a traditional model of exchanging money for a product or service. If you don't pay for the good or service, you have no "rights." If someone asks me for money and I unknowingly give them a counterfeit bill, for them to become angry with me for that would be wrong on their part. At that point you just stop having contact with them. Brian Wood http://webEbenezer.net (651) 251-9384
From: Leif Roar Moldskred on 12 Feb 2010 16:14 In comp.lang.java.programmer Brian <coal(a)mailvault.com> wrote: > > That is true in a traditional model of exchanging > money for a product or service. If you don't pay > for the good or service, you have no "rights." That's quite simply not correct. -- Leif Roar Moldskred
From: James Kanze on 12 Feb 2010 16:22 On Feb 11, 9:33 pm, Andy Champ <no....(a)nospam.invalid> wrote: > Lew wrote: > > Andy Champ wrote: > >> In 1982 the manager may well have been right to stop them > >> wasting their time fixing a problem that wasn't going to be > >> a problem for another 18 years or so. The software was > >> probably out of use long before that. > > Sure, that's why so many programs had to be re-written in 1999. > > Where do you get your conclusions? > Pretty well everything I saw back in 1982 was out of use by > 1999. How much software do you know that made the transition? > Let's see.. Operating systems. The PC world was... umm.. CP/M > 80? Maybe MS-Dos 1.0? And by 1999 I was working on drivers > for Windows 2000. That's at least two, maybe three depending > how you count it, ground-up re-writes of the OS. > With that almost all the PC apps had gone from 8 bit versions > in 64kb of RAM to 16-bit DOS to Windows 3.1 16-bit with > non-preemptive multitasking and finally to a 32-bit app with > multi-threading and pre-emptive multitasking running in > hundreds of megs. > OK, so how about embedded stuff? That dot-matrix printer > became a laserjet. The terminal concentrator lost its RS232 > ports, gained a proprietary LAN, then lost that and got > ethernet. And finally evaporated in a cloud of client-server > computing smoke. The "standard" life of a railway locomotive is thirty or fourty years. Some of the Paris suburbain trainsets go back to the early 1970's, or earlier, and they're still running. > I'm not so up on the mainframe world - but I'll be surprised > if the change from dumb terminals to PC clients didn't have a > pretty major effect on the software down the back. Have you been to a bank lately, and seen what the clerk uses to ask about your account? In more than a few, what you'll see on his PC is a 3270 emulator. Again, a technology which goes back to the late 1960's/early 1970's. > Where do you get your conclusions that there was much software > out there that was worth re-writing eighteen years ahead of > time? It depends on what you're writing, but planned obsolescence isn't the rule everywhere. -- James Kanze
From: Seebs on 12 Feb 2010 16:19
On 2010-02-12, Leif Roar Moldskred <leifm(a)huldreheim.homelinux.org> wrote: > In comp.lang.java.programmer Brian <coal(a)mailvault.com> wrote: >> That is true in a traditional model of exchanging >> money for a product or service. If you don't pay >> for the good or service, you have no "rights." > That's quite simply not correct. It had better become correct, if we don't want to trash all our economies again. If you have liabilities to people who grabbed free stuff off the internet labeled as providing no warranty, no one can afford to give anything away, and it turns out that there's a huge economic efficiency boost to allowing people to give away software. Solution: Let people give away software with no liability or warranty. -s -- Copyright 2010, all wrongs reversed. Peter Seebach / usenet-nospam(a)seebs.net http://www.seebs.net/log/ <-- lawsuits, religion, and funny pictures http://en.wikipedia.org/wiki/Fair_Game_(Scientology) <-- get educated! |