I was just reminded of the time not too long ago when we were upgrading our systems from (then) SUNOS to SOLARIS. A mildly frustrating experience! We came up with the acronym:
Sh*t Out of Luck And Rational Intelligent Solutions.
Perhaps someone could get the DMA 1-800 number got onto their own call lists. It would start some infinite recursion and the DMA stack would blow [wishful thinking on my part:) ].
Diebold makes hardware and (I'm assuming) software for ATMs. They seem relatively secure and foolproof to me. After reading the article, it seems Diebold has not applied any of their experience in the ATM business to the design and implementation of the voting machines.
As a children growing up in the 70's my brother and I were allowed to watch Looney Toons. As everyone knows, characters regularly got shot, blown up, etc. [Wile E. Coyote making weapons of mass destruction...yipes!]. Our parents let us watch the show with no problems. My brother and I turned out ok later in life (we're now both software engineers - maybe I use the term 'ok' loosley here;-) )
I was just wondering what everone thinks about
the differences between growing up in the 70's and growing up now?
A few years ago, I worked for a company which wanted to outsource sofware development work to a group of Pakistani programmers in Indonesia. I was assigned the responsibility of getting them accustomed to our development environment. Due to the language differences, it was quite difficult. In the end, my company scaled down the expectations for the consultants. This illustrated a couple of points:
1) Outsourcing development adds the obstacles of distance and possibly language differences to the task of training developers.
2) Not only are you now dealing with getting requirements right with the client who wants the software, you have to clearly communicate requirements with your second 'client' - the outsourced developers.
The above difficulties, I believe, reduce a project's chances to succeed. Add to this the possibility of bad code, back doors, etc deliberately placed into the code and you have some convincing reasons why outsourcing software development to groups outside the US is not a good idea.
Slashdot Mirror
I was just reminded of the time not too long ago when we were upgrading our systems from (then) SUNOS to SOLARIS. A mildly frustrating experience! We came up with the acronym: Sh*t Out of Luck And Rational Intelligent Solutions.
Perhaps he could bring it to a bowling alley? I'm sure it would do wonders for a 7-10 split :)
Wonder if he's got a 'spare' one lying around...
Diebold makes hardware and (I'm assuming) software for ATMs. They seem relatively secure and foolproof to me. After reading the article, it seems Diebold has not applied any of their experience in the ATM business to the design and implementation of the voting machines.
As a children growing up in the 70's my brother and I were allowed to watch Looney Toons. As everyone knows, characters regularly got shot, blown up, etc. [Wile E. Coyote making weapons of mass destruction...yipes!]. Our parents let us watch the show with no problems. My brother and I turned out ok later in life (we're now both software engineers - maybe I use the term 'ok' loosley here ;-) )
I was just wondering what everone thinks about
the differences between growing up in the 70's and growing up now?
A few years ago, I worked for a company which wanted to outsource sofware development work to a group of Pakistani programmers in Indonesia. I was assigned the responsibility of getting them accustomed to our development environment. Due to the language differences, it was quite difficult. In the end, my company scaled down the expectations for the consultants. This illustrated a couple of points: 1) Outsourcing development adds the obstacles of distance and possibly language differences to the task of training developers. 2) Not only are you now dealing with getting requirements right with the client who wants the software, you have to clearly communicate requirements with your second 'client' - the outsourced developers. The above difficulties, I believe, reduce a project's chances to succeed. Add to this the possibility of bad code, back doors, etc deliberately placed into the code and you have some convincing reasons why outsourcing software development to groups outside the US is not a good idea.