Don't Shoot Me, I'm Only the Software 392
ctwxman writes "How often have you heard about some massive crash and then the blame was placed on the software? "Disasters are often blamed on bad software, but the cause is rarely bad programming." If you've been looking to blame your boss, this article from MSNBC says your ship has come in! Poor planning, poor execution and poor leadership are more likely to blame than bad code when it comes to systems that fail. "
Irony (Score:3, Funny)
Although legitimate in the concept, I would say that poor programming is most definitely a cause for system failures.
Yikes... (Score:1, Funny)
MSNBC says your ship has come in! (Score:1, Funny)
So this bluescreen of death... (Score:4, Funny)
Re:Irony (Score:3, Funny)
"Damn it Bill, I'm a programmer, not a miracle worker!"
Sorry, couldn't resist.
Re:And the net/net is...A N D (Score:4, Funny)
We need to hire MORE managers.
I hate smoking software problems (Score:3, Funny)
%^$#@& SOFTWARE!!!!
UI and errors (Score:4, Funny)
In the generic sense, it would start with "Could not do xyz. Please check what you intended to do and try again."
Then, it would progress through "I can't do that. Try again." "You're starting to wear on my nerves. Can't you do anything right?"
Then, it would start to get more down to the source of the problem, beginning with "DOES NOT COMPUTE" and ending, finally, with "You fucking moron, my program works, read the manual before i cut you."
Stupid users always bothering me with [rottentomatoes.com] crap [rottentomatoes.com].
Re:Irony (Score:1, Funny)
Except for open source projects like... Fedora and Mandrake with their "Sure it erases NTFS partitions, but we'll release it anyway" distributions.
Re:MS employees (Score:2, Funny)
Re:Irony (Score:2, Funny)
but unfortunately they are with the money