Details
-
AboutDummy in programming
-
LocationEstonia
-
Github
Joined devRant on 2/3/2017
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
-
Sometimes when I'm writing Javascript I want to throw up my hands and say "this is bullshit!" but I can never remember what "this" refers to
#oldbutgold12 -
My Friend: Dude our Linux Server is not working anymore!
Me: What? What did you do?
My friend: Nothing I swear!
Me: But you were last on it?
My friend: Yes. I just wanted to run a bash file and needed to give it permissions.
Me : WHAT DID YOU ENTER???!
My Friend: Chill man, just this command I found on the internet
chmod -R 600 /
chown -R root:root /
Me: WHY ARE YOU EVEN IN ROOT AND GOD DAMMIT WHY ARE YOU EVEN USING SOME RANDOM COMMAND FROM THE INTERNET. YOU KNOW YOU SHOULD NOT DO THIS OR JUST ASK!
My friend: Ok I did something wrong, how can I fix it?
Me: Did you make a backup or rsync of the server?
My friend: No. I just wanted to run this file.
Me: You holocausted the server. FUCK MY LIFE35 -
Client: There is a high severity production issue.. you need to fix urgently..
Developer: I am on the way.. Will fix it once I reach home.
Client: I don't care where you are. Fix it right now😡😡
Developer14 -
Client not paying?
Instead of reducing opacity, add FartScroll until they pay!
Theonion.github.io/fartscroll.js5 -
!rant
Wow. Compared to some other online developer communities (coughcoughStackOverflowcough), devRant is AMAZINGLY light-hearted and welcoming. Great job, everyone here. :)5 -
"Knock Knock"
"Who's there?"
"Knock Knock"
"Who's there?"
"Knock Knock"
"Who's there?"
- DoS Attack20 -
A little bit of Lua in my life
A little bit of Java by my side
A little bit JS is all i need
A little bit of bash is what i see
A little bit of JSON in the sun
A little bit of Python all night long
A little bit of TCL here i am
A little bit of this makes me your dev17 -
"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 -
Left one of the demo macs at Best Buy with vim running on a terminal shell. Let's see how long it takes for them to exit vim.5
-
Told my colleagues about devRant and they laughed it off saying that it's just 'another app'.
Fuck them.10 -
I was looking for about a month for a laptop. Then on this one magical day I open kijiji and see a Toshiba Thinkpad T450s with 20gb of ram, 138 ssd and an i5-6300U cpu going fo 500$ (value 2000+).
My first thought was. Okay. Scam alert. But you know. What if?
So I call up this person. And its a girl who got a pc from her bf, but really she wanted a mac so she is selling it.
This straight up blew my mind. I decided, fuck it. Got 500. Ran to her. Ran a systems check on the laptop. Checked for any attempts at opening it up. Checked the harddrive. Checked the ram. Everything is solid.
Long story short. Thank god for apple fangirls!32 -
ERRORs are red,
INFOs are blue.
My logs look pretty,
But not as pretty as-
Wait, hold on. Why are there ERRORs in here?
Why is the homepage returning a 5- oh crap.
Can you just... Can you give me a minute?12