• pitchingchris (cs)

    the best part of this story is missing - its how they treat ken after all this crap happens. More than likely they'll shrug it off and everything will go back to normal, with Ken still barking at everybody, which seems to be the WTF, but it always happens.

  • Ceiswyn (unregistered)

    Yes, but WHAT HAPPENED NEXT?!

  • MC (unregistered)

    And then Ken found 5 dollars? Where's the rest of the?

  • Blablablaadje (unregistered)

    Missing the fun part :(

  • Dlareg (unregistered)

    Garret got a nice bonus. Plus he can now install whatever he wants.

    I always make these kinds of deals, there is never any budget for bonuses and stuff. But if you do this overtime, you get a new development laptop to use at home :wink wink: or I get to order from our electronics supplier etc... (different budgets)

  • Code Dependent (cs)

    Ken, meet Garrote.

  • pjt33 (cs)

    These stories work best when you anonymise them consistently. I presume that the sentence

    "No fuel?!," Ken responded, "it holds over two hundred gallons! Is there a leak, or some way for the fuel to escape?"
    requires s/Ken/Garrett/ ?
  • Uhhh (unregistered)

    The real WTF is that I read this one. It really did just seem to

  • Anonymous (unregistered) in reply to pjt33
    pjt33:
    These stories work best when you anonymise them consistently. I presume that the sentence
    "No fuel?!," Ken responded, "it holds over two hundred gallons! Is there a leak, or some way for the fuel to escape?"
    requires s/Ken/Garrett/ ?

    Proofreading is hard.

  • Scouse (cs)

    You accidentally the whole

  • Troy (unregistered)

    THEN WHO WAS

  • amischiefr (cs) in reply to Ceiswyn
    Ceiswyn:
    Yes, but WHAT HAPPENED NEXT?!
    Like any good book, it keeps you wanting more. You'll be stuck to this site waiting for the next release.
  • DOA (cs)

    Warning bells started ringing as soon as I saw ex-military in a software development company.

    It's like hiring an ex-janitor as a surgeon.

  • lolwtf (cs)

    So wait, Ken was speaking in the third person?

  • Populus (unregistered)

    These ex-Navy guys are the worst. They have to have procedures and manuals for everything else they wouldn't know how to turn on a light or go to the bathroom.

  • ounos (cs)

    There was an IT manager who wrote procedures to be followed. One day it was discovered that he didn't follow one procedure. The result was

  • someguy (unregistered) in reply to DOA

    Or an ex-surgeon as a janitor.

    They're entirely different fields, and while I'm of the general opinion that programmers are awesome enough to bring a unique and useful perspective to any situation, most job skills do not translate well.

    Surgeons may be really smart and really highly trained- but not at being janitors. And they'd probably be horrible at it.

  • gpb (unregistered)

    And he would have gotten away with it if it weren't for those meddling kids?

    Story FAIL

  • meeee (unregistered)

    i guess that's standard military service behavior: before you go home, make sure to fill up with free diesel (greetings to all swiss army members hehe)

  • Luthe (unregistered) in reply to someguy

    bah, how many programmers truly know garbage collection.

  • Anonymous (unregistered)

    Well, that sucks, but TRWTF is that people are so willing to work under shitty managers. That and the fact that the story never really

  • Garrett (unregistered)

    hey tdwtf I need your help I accidentally the end of the story what should I do...

  • You didn't see me right (unregistered)

    I was going to write a witty comment but

  • blah (unregistered)

    /*

  • kmarsh (cs)

    Watch out for anyone named Ken.

  • Anonymous Coward (unregistered)

    To everyone complaining that the WTF is missing the end, presumably the implication is that Ken has been siphoning the diesel in the generator after every "test" and getting maintenance to top it up, essentially embezzling his car fuel costs from the business. Do you need everything spelt out for

  • Steve (unregistered)

    Well, it took me a while but I finally figured it out. What you're basically saying is that

  • Code Dependent (cs)

    <lemming>All you guys leaving off the ends of your sentences are really starting to </lemming>

  • Rob (unregistered)

    But that's how real life works. You don't always get the ending, so you're free to write your own.

    It might be the one where Ken gets fired the next day.

    It might be the one where Garrett gets fired the next day.

    Or it might be the one where someone installs cameras without Ken's knowledge and posts the video of Ken siphoning the generator fuel on YouTube.

    Whichever one fits your worldview (or come up with your own)... :)

  • Leo (unregistered)

    Garrett accidentally the whole WTF.

  • Some Guy (unregistered)

    Are we sure this guy's name wasn't Jack? As in Candleja

  • GCU Arbitrary (cs) in reply to Anonymous Coward
    Anonymous Coward:
    To everyone complaining that the WTF is missing the end, presumably the implication is that Ken has been siphoning the diesel in the generator after every "test" and getting maintenance to top it up, essentially embezzling his car fuel costs from the business. Do you need everything spelt out for
    Whilst it is implied that Ken's embezzlement is discovered by the CEO and he (Ken) then spends the next five years in PMITA prison, it is by no means certain since the end of the story is
  • Bim Job (unregistered) in reply to Code Dependent
    Code Dependent:
    <lemming>All you guys leaving off the ends of your sentences are really starting to </lemming>
    Well, lemmings jump off the end of a cliff, so why shouldn't they leave off the end of their?

    Also, fruit flies like a.

    What's the deal with Photo Guy's hair, anyway? I mean, I'm bald, but even I'm not desperate enough to wear an Ena Sharples hairnet circa 1963, plant my head with rag-weed, and then try to out-Chia Chia...

  • Steve H (unregistered)

    In b4 Belair

  • Inno (unregistered)

    I'm sure Ken owns a Hummer so

  • Airhead (cs) in reply to ounos
    ounos:
    There was an IT manager who wrote procedures to be followed. One day it was discovered that he didn't follow one procedure. The result was

    Yes, I've heard about this same thing. It was actually quite funny when

  • Durr (unregistered) in reply to ounos
    ounos:
    There was an IT manager who wrote procedures to be followed. One day it was discovered that he didn't follow one procedure. The result was

    Nominating for best post all week

  • Inno (unregistered) in reply to Inno
    Inno:
    I'm sure Ken owns a Hummer so
    ... he was always short on diesel.

    [There! Completed that for you!]

  • Maurits (cs)

    it's supposed to be topped off after every test

    There's the end of the story, right there... brilliant (with two "i"s.) Like the Sixth Sense, you now have to go back and read the story from the beginning again to fully appreciate it.

  • Joey Stink Eye Smiles (unregistered)

    I'd bet money that the janit-, uh field tech, simply didn't turn off the generator after the last test and then didn't refuel it.

  • @Deprecated (unregistered)

    It's a "Pick your own ending" book!

    If you want Ken to be fired, turn to page 39. If you picked up the magic shoes in the crystal cave, turn to page 17. If you think Garrett now has a new best friend, turn to page 128.

  • Herohtar (unregistered) in reply to @Deprecated
    Comment held for moderation.
  • anonymous coward (unregistered)

    The real WTF is that the developer even tried to use VBA while he should have warned his manager(s) that he couldn't develop if he couldnt get freaking dev tools.

    This is ridiculous.

  • Satanicpuppy (cs) in reply to pitchingchris
    pitchingchris:
    the best part of this story is missing - its how they treat ken after all this crap happens. More than likely they'll shrug it off and everything will go back to normal, with Ken still barking at everybody, which seems to be the WTF, but it always happens.

    Yep. I just had one like that earlier this week. Stupid manager demanding high priority code changes to accommodate an upcoming product change, and they ditched the product change at the absolute last possible second, which caused untold havok with all the code which was suddenly wrong (well, not wrong, but the supply chain is set more than a week in advance, and so the stuff that's been being scheduled for the next 7 days is all wrong, and needs to be rescheduled and rushed with literally hours until production).

    If the course of events had been reversed, if they had gone live and my code was wrong, I would have had a bad time of it (well, I would have had lots of meetings and talks from my superiours, who, none-the-less, wouldn't have fired or reprimanded me in any meaningful way, for fear I'd snap and kill someone, or, worse, quit), but since it's someone else's fault, even though its cost thousands of dollars and hundreds of hours, it'll just get swept under the rug.

    Way of the world. Management is seldom held responsible for their own bad decisions.

  • WT (unregistered)

    wow that is like 3 WTFs in one article

  • Lars Vargas (cs)

    The WTF reminds me of certain episodes of "The Brady Bunch" or "Gilligan's Island" or "Three's Company" where the show ended with no story completion and then showed "to be continued...".

    Except there's no "to be continued..." here.

  • Code Dependent (cs) in reply to Satanicpuppy
    Satanicpuppy:
    ...and they ditched the product change at the absolute last possible second, which caused untold havok with all the code which was suddenly wrong
    Three words: source control rollback
  • Code Dependent (cs) in reply to @Deprecated
    @Deprecated:
    If you want Ken to be fired, turn to page 39.
    Court-martialed would be more appropriate.
  • Peter (unregistered)

    what's the procedure for installing a camera?

  • jmucchiello (cs) in reply to DOA
    DOA:
    It's like hiring an ex-janitor as a surgeon.
    Or in this case hiring the janitor as a field tech.

Leave a comment on “Double-Standard Operating Procedures”

Log In or post as a guest

Replying to comment #:

« Return to Article