Slashdot Mirror
Calling Software Reliability Into Question
phillymjs writes "CNN is running a story on software reliability, and how the lack of it may cost more and more lives as technology creeps further into everyday products. It appears a debate is finally starting amongst everyday (read: non-geek) people about vendor liability for buggy software. Some opponents of the liability push are unsurprising: Says the story, 'Microsoft contends that setting [reliability] standards could stifle innovation, and the cost of litigation and damages could mean more expensive software.' The article also says, however, that consumers' favortism of flashy products over reliable ones is partly to blame for the current state of software."
..file for bankruptcy because you're paying people to do all this while not having a product to put out.
That Jesus Christ guy is getting some terrible lag... it took him 3 days to respawn! -NJ CoolBreeze
Wow, so it's either assembly or nuthin, huh? That's kinda lame. Granted, it's very valuable to know the diff between a stack and a heap, but that's not the end all of everything.
And frankly, after leading teams, the last thing you should do is fire people on it. I would suggest letting go of clueless managers and real payroll hogs. Then teach/mentor your jr. level programmers. I dunno, being l33t like that actually will hurt a project more than help.
Also, Step 9.5 should be refactor, test, repeat 9, since that's ususally how it goes.