Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@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. -
@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. -
@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. -
@nmunro aaand I'm saving that one for future use. Thank you for improving the way in which I give feedback! 😁
-
@nmunro If in doubt - C4.
-
@Ghosty Is that strapped to the computer or the person?
-
@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.
-
@nmunro Strapped to the problem, of course ;)
-
@filthyranter wow Thanks thus Made Le laugh Three Minutes straight
-
@cdrice maybe you should send them the gif in this https://www.devrant.io/rants/197450
-
@nmunro Saving that so hard for future use.
-
@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. -
@cdrice I disagree, be mad that they have a job they are obviously too incompetent for.
-
@mhudson 😂
-
@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...
-
@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. -
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 -
@DoctorWhatIf unless due to cultural reasons, the authority actually supports the "rabble rabble" guy...
-
sorry for you man, that really sucks and hurts.
However, it's the best trick I ever heard. I'll play it when I'll be on the other side and feel like being a real asshole.
I'll say:
- yeah...we run that guy scripts and it didn't work
- well, we also had to change some little unnecessary things he did because they were not clear at all
- so we even *worked* to fix something he did, we are left with an unusable system and he doesn't want to help
- he didn't even took care of documenting the problem
On the other side, if I were you, I'd be laughing for days and let them eat their own shit -
Hahaha OMG brings back memories. A client is converting into a new version of their ERP system and of course they had to test with the new version. On one issue ite took me about two days to find which objects it passed through only to discover lo they commented out whole blocks of code. This was the strategy of the vendor for customizations done by the client to their system. It's good to be able to laugh now 😁
-
I do that when I don't understand some code, but when somethings goes wrong I contact the author to ask or decribe it (not to blame) for me.
Some author is nice and fully describe the detail about the code, some of them is just say "it's important" or "that the requirement of something" and it okay for me as long it's working.
Is good to know about how the code work, but with your case I just don't have a word to say maybe a chair will make more meaning than any word. -
@tsloterman I like the fact they commented parts of his code and asked him to fix it
"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.
rant
fml
upgrades
morons
automation
scripting