in reply to Re^3: Perl in the Enterprise
in thread Perl in the Enterprise

You're right, that is an idiotic idea. I don't know why he thinks that has anything to do with "enterprise." Military applications are almost the opposite of enterprise coding.

Replies are listed 'Best First'.
Re^5: Perl in the Enterprise
by jdporter (Paladin) on May 18, 2006 at 20:27 UTC
    Military applications are almost the opposite of enterprise coding.

    I'm guessing to you "military" means something like aviation control or weapons targeting systems.

    But "the military" is an enterprise in itself. The U.S. DoD is the largest, most complex organization in the world. They do indeed have "enterprise" systems, for things like logistics management.

    We're building the house of the future together.
      "Enterprise" systems usually refer to the in-house custom apps that businesses write for their own use and don't sell to anyone, e.g. "that thing Bob wrote that lets the merchants check how many foozits were purchased but not shipped yet". As anyone who has worked on such systems knows, these are almost uniformly the worst code imaginable. Most of them don't scale, have no tests, and are held together with chewing gum. It is possible that things are just as bad in the non-weaponry side of military coding, but I hope not.

        Then you really are unfamiliar with governments, bureaucracies, and militaries. :-)

        We're building the house of the future together.

        By the same logic, I used to think that the systems that run transactions at banks must hold up to the highest standards, and that this is why banking IT is so conservative. Note I am using the past tense…

        Makeshifts last the longest.