Details
-
LocationDenmark
Joined devRant on 11/8/2016
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
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I love this new description for my job... Programming: pressing plastic squares in more or less the right order... 😂
@phrawzty3 -
Dev: Microsoft is shit
VS Code: (ಥ⌣ಥ)
Dev: Oh not you dear! You're not like the other guys
VS Code: (。◕‿◕。)45 -
*Me and my workmates laughing and having fun before going home*
Me: Hey, do you want to hear a joke?
Workmate 1: What is it?
Me: Look at your code.
...
...
...
Other workmates: BURRRRRNNNN!!!!4 -
This vacations I decide to learn c# in VS, and this is the result, a personal agenda, where I can to save my qualification or homework, I think that vs is a good ide for work and replace to java from my ❤4
-
Ghost in the Shell (2017)undefined ascii i need to study for exams shell i have too much free time ghost bash ghost in the shell28
-
"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.105 -
I just realized that CPU's are essentially electronic hookers, for processes.
They'll service any process that calls upon them, but keep switching between various processes so that it can spend time fairly with each of its processes. And of course, they'll immediately abandon their current process if one with a higher priority reveals itself and attend to that one instead. Once it is finished, it'll return to its less-important processes.
Kinda sounds like a hooker to me... 🤔4 -
I was just thinking... The JetBrains devs must enter the office and be like:
"Today I'm gonna program a programming program for others to program, and I'll do it on the programming program I programmed last year."4 -
Note to myself : Searching "String LaTeX" on google might give you something quite different from what you expected2