Slashdot Mirror


IT Myths

linuxwrangler writes "A special report in this week's InfoWorld tackles the six big myths in IT. Among the findings: server upgrades don't matter, 80 percent of corporate data is not on mainframes, C[IT]Os really do need technological savvy, most IT projects may be late or over budget but they don't fail, IT does scale and nearly all big shops do run multiple platforms."

4 of 380 comments (clear)

  1. Re:Other IT Myths by ackthpt · · Score: 5, Interesting
    that is now hanging up in my cube. bless you.

    This was haning in the Programming Office where I once worked. The word was it dated from the late 70's. That you and I identify with it today says something.

    --

    A feeling of having made the same mistake before: Deja Foobar
  2. Re:Other IT Myths by sql*kitten · · Score: 5, Interesting

    What we need to do is to get organized and support independent regulation authorities which will prevent companies from doing anything they think its cheaper.


    There is an organization in the UK, the Institute of Analyst Programmers, that bills itself as a professional organization for programmers. I am a member and every now and again I badger them about getting a royal whatever so members could qualify as Chartered Engineers (or whatever title), like the IEEE, the IMechE and so on.

    Their reply? Pursuing that is not in their members best interest, as most of 'em would fail to qualify and quit, leaving the IAP without any members and hence funding. There is a rival organization, the BCS, but their chartered status is like an MCSE, no-one bothers to get it, no employer ever demands it.

    Ultimately, it needs to be demonstrated to both programmers and employers that some sort of accreditation actually adds value, 'til then, it won't ever be accecpted. Face it, if a bridge collapses that matters, if the database is the wrong shade of mauve your PHB might get upset but really, who cares?

    Of course embedded is different, but that's often done by EEs who can get chartered.

  3. Re:Another myth by hoggoth · · Score: 5, Interesting

    > It's only a prototype - we're not going to deploy it in production.

    Oh... this brings back painfull memories.
    Years ago I was working at a mid-sized systems integrator (several hundred staff).

    My manager told three of us to 'whip up a demo' of what a document imaging system might look like to show the company owner. So we read a few IT magazines about document imaging, and cobbled together a program WRITTEN IN A SPREADSHEET, that had three buttons:

    Button 1, 'Scan', would scan an image and display it.
    Button 2, 'Save', would save it to disk with a title and page number.
    Button 3, 'Workflow', would throw up a spreadsheet of the documents with a column where you could enter a staff persons name.

    It took us a day or two and then we showed it to the manager. He loved the concept and showed it to the owner. He loved our hot new product and showed it to sales. Sales loved our new strategic direction and showed it to clients.

    A big power utility bought it for mega-bucks.
    As the designers who built the thing, of course we had to install it on site and do the training.
    They were expecting a full blown document imaging system with complex workflow paths etc etc.

    I'm sure if any of the other guys on that team are reading this they will recognize this story at once.

    --
    - For the complete works of Shakespeare: cat /dev/random (may take some time)
  4. Myth 7: IT Journalists know the field... by gillbates · · Score: 5, Interesting

    Its amazing just how little these supposed journalists truly know.

    Any technology is scalable...

    Really? I happen to know of a case where someone was fired because they believed this religiously; they insisted that any performance issues the new system might produce could be handled with a server upgrade.

    So they upgraded the server, and what do you know - response times fell. From 300 seconds to 90. The system still wasn't usable, and the manager was fired. Perhaps the most embarassing part was the fact that a back-of-the-napkin analysis would have revealed the flaws in the "Use disk space for memory" design.

    Most IT projects fail...

    Well, well. This is spin at its worst. Yes, only 34% of IT projects come in on time. Another 50% are "a day late and dollar short..." - that is, after the project schedule slips, they end up shipping a product with missing features. General hint for journalist: if you have to redefine words to prove your point, you're probably not telling the truth.

    No, perhaps 70% of projects aren't unmitigated failures, but I'll bet that IT projects fare far worse than other industries:

    • How many unfinished bridges do you know of?
    • How many unfinished housing projects can you name?
    • How many unfinished/incomplete decks and swimming pools have you seen?
    • How many times do EE's scrap a project after a successful prototype has been built, due to project management failure?
    • How many automobile engine projects have failed? The last I can remember is Chevrolet's Vega engine - glass lined cylinders should have been a tip-off right there....

    Yup, IT is still at the bottom of the barrel when it comes to delivering on promises. Not good.

    --
    The society for a thought-free internet welcomes you.