• M L (unregistered) in reply to Nicholas
    Nicholas:
    I typically work on multi-hundred-KLOC systems, including compilers and molecular simulators. My code usually has few problems. The problems I run into are usually subtle race conditions or failure to observe zero-copy semantics.

    I'm sure you also have a killer smile and a huge dick, Lyle.

  • Tyler (unregistered) in reply to Anon

    I'm currently working in NYC as part of a small group that's doing automated trading. We test everything very thoroughly through all stages of developmement. I'm pulling in 100 K + bonus (which is dependant on performance (last year's was 275 k))

  • p (unregistered) in reply to Outlaw Programmer
    Outlaw Programmer:
    JC:
    John:
    And - most places I've worked at have done this, at least to some extent.

    Financial institutions really ought to know better though

    Financial institutions seem to be the worst for this sort of stuff in my experience. I used to work at Lehman Brothers and we had several similar instances caused by lack of testing and a general, we need it in there ASAP attitude.

    This mirrors my (limited) Wall St. experience, too. Everyone in management hated the idea of testing. Most clients just could not grasp the concept of testing. Yes, you're buying extra hardware for the QA layer but you will save thousands (millions?) in the long run, dammit! Clients that actually did buy servers for QA would often neglect them so that they became wildly out of sync with their production systems.

    Eventually, the company motto became, "We'll test it in production!"

    Look..you test it in production.

    If it works, you turn it over into QA.

    EVeryone knows that!

  • Lyle (unregistered) in reply to M L

    Actually, my smile is kind of weaselly, and my penis is microscopic, but thanks for trying to cheer me up.

  • (cs) in reply to Bill O'Reilly
    Eventually, the company motto became, "We'll test it in production!"
    WE'LL DO IT LIVE!

    The sad thing is that far too many managers actually say exactly this. I remember when I started working at a new company some years back and I had just implemented a new feature. I had not even run the unit tests yet, just hitted save in my IDE and started up the app to see what it looked like. The manager came to me and liked the feature so much that he said: let's deploy it right away! I objected and said it needed some testing, but he wouldn't hear of it: "We have thought of a very smart system to do things and safe time and efforts. We'll test live". I was stunned...

    For the rest of the hour I tried to reason with him, trying to explain that a bug at one place could potentially bring down the entire system, but he simply couldn't grasp the concepts involved. For him "testing" was just getting feedback about how clients liked something. E.g. when "testing" how people like a new color. To him a new feature was like a new color. Totally oblivious to the fact that it could possibly hurt something.

  • (cs) in reply to Tyler
    Tyler:
    I'm currently working in NYC as part of a small group that's doing automated trading. We test everything very thoroughly through all stages of developmement. I'm pulling in 100 K + bonus (which is dependant on performance (last year's was 275 k))
    Nice!

    Now, can you put the words "professional" and "worthwhile member of society" together without giggling?

    PS Ignoring the solecism of "pulling in," you might want to check your spelling. It's "development" and "dependent."

    The former, I can forgive as a typo. The latter suggests that you're a worthless moron.

  • probable poster (unregistered) in reply to powerlord

    how could one be certain?

  • (cs)

    I have this article bookmarked in case anyone asks me how Knight Capital happened.

Leave a comment on “Deploy! Deploy! Deploy!”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article