Get the app to ++, post and comment
  • 1564

    "You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

    So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

    First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

    So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

    Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

    I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

    Did you run the code I gave you to do this update?

    "Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

    So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

    More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

    I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
    Finally someone breaks the silence and explains.

    And this, my friends, is the part I will never forget.

    "We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

    You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

    "Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

    I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

    So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

    You just cannot make this kind of stuff up.

  • 221
    Thank you for this real rant in a long time. I hope you getting much ++
  • 60
    yep, good rant.

    Thx for sharing your hate.

    Do you know anything about the cultural background of the guy commenting out the code?

    Sounds a bit like a "not losing face" kind of thing...
  • 61
    Sounds like you should gtfo of that place
  • 27
    @tambo That is a very fair question, indeed. I have run into similar cultural issues working across an international team before. I feel quite confident in this case, though... this was a case of just being straight-up clueless.

    I have the feeling someone on their team was trying to learn automation, and using my code as some sort of learning exercise... which is fine if it's just for testing or a sandbox or whatever... but running that on production? It just boggles the mind.
  • 8
    @Ronald I've had that inclination many times... but I am a full-time work-from-home employee, and that's hard to walk away from. But days like that, the WTF-stress really does take a toll...

    Luckily this team isn't one I have to interface with any more... and I doubt they are going to come back to us/me for any more automaton after that debacle.
  • 20
    @tambo @cdrice Being an expat, and working in a multicultural environment myself, I realize there can be cultural differences that boggle one's mind.
    However, in this case I think it's plain old stupidity and ego at play.
  • 8
    Wow, just... Wow.
    I'm glad that, as you mentioned, you don't have to deal with those people anymore.
    There should be an authority to whom we could report these kinds of thing...
  • 29
    Reading your rant, made me hate those people, though I don't know them, but now I am super pissed at them.
  • 56
    I have an image like this at work that I use from time to time in situations like this.
  • 7
    @nmunro aaand I'm saving that one for future use. Thank you for improving the way in which I give feedback! 😁
  • 6
    @nmunro If in doubt - C4.
  • 6
    Humans... They are stupid AF
  • 3
    Too bad you didn't wrote what you say to those guys. I m sur it was very... Colorful ^^
  • 9
    Wish I could upvote this more. Somebody is in dire need of a stress ball.
  • 4
    Fucking hell dude, I only can imagine a fraction of how pissed you were.

    Come, here, take a ++
  • 4
    If I could give you multiple ++ I would.
  • 3
    @Ghosty Is that strapped to the computer or the person?
  • 4
    @nmunro Baaaaaahahahaha! I actually used that phrase while describing this situation to my manager. With a healthy dose of "Thaaaaaaar's". The Walrus is my spirit animal.
  • 4
    @nmunro Strapped to the problem, of course ;)
  • 8
    Holy mother of rants, finally a good rant! I had a good laugh when the comment-it-out-thing happened xD
  • 4
    @filthyranter wow Thanks thus Made Le laugh Three Minutes straight
  • 5
    WHOO HOO!

    Just hit 300; thanks everyone! You can never have enough things to squeeze on. Wait, what?
  • 4
    @cdrice ( ͡° ͜ʖ ͡°)
  • 20
    I wonder what happens if these geniuses ever opens the hoods of their cars. If their standard procedure is to remove everything they don't understand, there won't be much left of the engines.
  • 6
    @cdrice maybe you should send them the gif in this https://www.devrant.io/rants/197450
  • 4
    I'm betting no recent backup of production either.
  • 6
    What if that was just true for everything? "Yeah didn't really understand how this jet engine worked, so I commented it out. Here's hoping my flight to Singapore is safe."
  • 2
    Oh wow...
  • 6
    Omg....you should punch them in the face...with a chair.
  • 3
    @akd5010 always a solid suggestion
  • 5
    @akd5010 made of steel
  • 3
    Gawd dayum! Here, have a 🍺
  • 3
    Awesome click bait.
  • 6
    I am still waiting for the follow up when you were prosecuted for murder
  • 5
    It's that kind of experience that just makes you think, "I... I can't help these people. They're just too stupid."
  • 3
    @nmunro Saving that so hard for future use.
  • 4
    I'm going to copy paste this into a word processor, give it a nice font, blow it up to like 75, print it on a poster, frame it, and hang it on the wall opposite my desk. Motivational poster. Did anyone make it through this without cracking up?
  • 4
    This is a good rant. I hope they all have two buttholes to poop put of now... you know, because you tore them a new one.
  • 2
    the management of their team is with iq below 50. anyone with common sense won't do this.
  • 5
    Yeah...
  • 1
    Good lesson for others to pack code (.exe,.......) so others cant comment code so easily
  • 2
    What the actual motherfucking fuck
  • 2
    What the actual f*ck! You work with a bunch of illogical dummies, I'm sorry for you dude.
  • 3
    Didn't they notice on their own how stupid that sounds?
  • 5
    @Krokoklemme No. To this day they insist they did nothing wrong.

    Just a few days ago we came across another issue their team caused with their "updated" install process (which now looks almost nothing like what I originally wrote for them). I notified them of the issue (and how to fix it) and they turned right around and said it was my code, so it must be my fault something else broke.

    Really unbelievable.

    I'm not even mad at them anymore though - they just don't "get it". You just can't be mad at someone you can't even have an intelligent conversation with.
  • 1
    @cdrice I disagree, be mad that they have a job they are obviously too incompetent for.
  • 6
    Hooooooooooooooooly shit. Uncomment. Re run. Demand heads and/or raise.

    Jesus Christ just reading the rant raised my blood pressure.
  • 2
    Your code is broken! It doesn't work with the changes I made to it!
  • 1
    Super relatable though. Shows how important it is to go through the steps a developer took when they say your thing isn't working because 99% of the time they forgot to do something or did something a little differently no matter how amazing your documentation or steps are
  • 0
  • 2
    Holy man that's brutal yet insanely funny at the same time (mainly because it's not happening to me I guess)
  • 3
    I was the thousandth ++ :D
    Anyway great rant, and just a bit of illumination. The code can't break if you comment it all out
  • 2
    Time to find another gig. Otherwise I hope you're getting paid way above average to deal with these wankers.
  • 6
    Your 1k plusses makes me wanna have super stupid co-workers now...
  • 2
    I am angry now.
  • 1
    What a story!
  • 1
    This is actually really dangerous xD Glad you got in there and fixed it
  • 1
    W-what?!
  • 0
    @Atari 100% true, I swear. Only the names and inconsequential details have been changed to protect the "innocent"... or at least to protect me from sharing too many details that I get in trouble...
  • 2
    OK, this is what confuses me. why didn't they just uncomment the code and test it as was given? I get they didn't understand it but why not test it and see if it runs well before accusing the author?
  • 2
    @KingSolo Exaaaaaaactly. What's even more bizarre is the entire process was very well-defined and already was tested and working for several months. I demonstrated it end-to-end during the turnover, and gave them ample opportunity to ask questions at any point (the formal turnover was over several days of meetings & classes, etc).

    The whole thing was pretty bullet-proof (until they started mucking with the code, of course). For the new update, all they had to do was drop the new payload files in a specific location and run the job. Absolutely nothing else. They completely fubar'd the process for reasons only they will ever understand.
  • 2
    I want to know what you said so much now :D
  • 2
    I would actually really like to know what you did and said afterwards? I'm not sure how I would react. Whether to speak with the people calmly and explain your point of view or going straight to the boss
  • 2
    I guess in their mind the situation was smth like this:

    This guy thinks his such a star, giving us speaches on his super baby. Who the f*** think he is?

    Let's give him some hard to find bug.
    And embarass him in front of the boss.

    Oh shit he caught us.

    We.... we wanted to.... We just commented the parts we didn't understand.

    Yeah...
  • 1
    I have developed a special nuclear weapon that kills only one person. It creates small mushroom cloud with pop sound and kills. Enough radiation that even satan would reject from hell for high radiation levels..

    This specifically works great with people like described above.

    Noob fucking shit! Dafaq
  • 0
    Those from that team are non-technical right?
  • 0
    Those from that team are non-technical right?
Add Comment