Slashdot Mirror


Don't Shoot Me, I'm Only the Software

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. "

2 of 392 comments (clear)

  1. Buck Passers by mfh · · Score: 4, Informative

    If you've been looking to blame your boss, this article from MSNBC says your ship has come in!

    I think this little gem says it all. Strangely enough, it's today's Dilbert. Thing is, the buck-passers are who protect their own image or the image of those who write their cheques. The result? Too many projects are blamed on interns or programmers, rather than the truth coming to light.

    Why? I think it's simple, really. Management often has no clue what they are doing in terms of managing a technical project so they make decisions about things like the exact features, and they often fight to get things a certain way -- unwittingly forcing programmers to code all the way around the block to get to the house next door, leaving problems in the wake.

    The best case is when a programmer is given design autonomy. That's why Open Source is such a threat to large companies like Microsoft... because the guys who know what *can* be done, are the same guys doing it -- the result is 1111x better, and cheaper too.

    I am so lucky to be working now for a company that allows me to have full autonomy with my projects. They tell me what the customer wants and I do it the way I think is best. Every single project done in this manner has resulted with happy customers and excellent systems.

    --
    The dangers of knowledge trigger emotional distress in human beings.
  2. Re:Fuck You Microsoft-NBC! by TrancePhreak · · Score: 4, Informative

    Way to troll doofus.

    The 49.7 days refers to stuff that is not based on Windows NT. IE Nothing to do with the system deployed that was Windows 2000. Second, the versions of Windows that are built this way do not require rebooting at this period, an internal timer turns over and the system continues on as normal. The programmer who designed the system for the FAA msut not have RTFM or designed it very poorly to require this.

    --

    -]Phreak Out[-