continued…
I'm In Canada. A woke HR lady hires an African guy despite him plagiarizing code and lying through an interview. First day he surfs soccer websites so I confront it and HR lady basically calls me a racist and to watch my back.

A second African new-hire comes into the office today and he seems quite capable in an area of specialization for our team. So I ask if we can have him on our team because he has skills. The exec decides to look at the costing for him and goes, "HOLY SHIT WHY ARE WE PAYING ANYONE THAT MUCH?" She looks at the résumé of the new guy and finds out that he is only at intermediate level in his specialization. So I say, "It could be worse. The other guy flat out lied through his interview and he got hired anyway." I forward the emails where I recommended against hiring the other guy and why.

My exec, who is a company stakeholder, opens the pricing list for recent hires. It is obvious that if you are not not white you get paid way above market value for your skill level. Exec is pissed off on a level I never knew was possible.

We make a call from the board room only to find out that the head of HR (also an executive) is driving this. My exec tells me to give her the room. The yelling was so loud everyone could hear what was said from outside the boardroom. At one point the HR lady says, "Just because we could get them cheaper doesn't mean that we should… We pay that much because it is 'the right thing to do'." My executive goes completely silent for a few seconds then in a super aggressive way says.

"…I am going to have your FUCKING head for this. Then I will make sure that you NEVER get a job in HR again for the rest of my natural life. ONLY ONE of us will survive this. YOU are the one pissing away profit. So get ready because I'm going to drown you and your team like a bag full of unwanted puppies." Then she hung up the Polycom. She came out about a minute later and kicked the office manager out of his office and sat there all day making calls and sending emails.

https://devrant.com/rants/2337768/...

Pro tip: If you are a junior, or senior but new at the company, don't start your conversations with:

"We're doing X wrong. At my previous company we did / at school I learned /in this book I read / according to this talk I watched, the right way to do X is ..."

Instead try:

"I'm curious why were doing X this way. I'm used to doing it differently."

I love flat-hierarchy teams, and people who think about flaws in procedures and proactively try to improve the tools we use are awesome, but the next kid walking up to me yelling we use git flow "wrong" will be smacked in the face with a keyboard.

If you come to me with curiosity and an open mind, I'll explain, and even return the favor by behaving the same way when I'm baffled by your seemingly retarded implementations.

Maybe we can learn from each other, maybe discover that "how I learned it" is sometimes good, sometimes bad.

But let's start with some social skills, not kicking off into every debate with a stretched leg and a red face.

When you're both a designer and a programmer at the same time

Spent most of the day debugging issues with a new release. Logging tool was saying we were getting HTTP 400’s and 500’s from the backend. Couldn’t figure it out.

Eventually found the backend sometimes sends down successful responses but with statusCode 500 for no reason what so ever. Got so annoyed ... but said the 400’s must be us so can’t blame them for everything.

Turns out backend also sometimes does the opposite. Sends down errors with HTTP 200’s. A junior app Dev was apparently so annoyed that backend wouldn’t fix it, that he wrote code to parse the response, if it contained an error, re-wrote the statusCode to 400 and then passed the response up to the next layer. He never documented it before he left.

Saving the best part for last. Backend says their code is fine, it must be one of the other layers (load balancers, proxies etc) managed by one of the other teams in the company ... we didn’t contact any of these teams, no no no, that would require effort. No we’ve just blamed them privately and that’s that.

#successfulRelease

Who remembers winamp? Well... We still use it in our bar once a year

Backstory: I help to organize a small openair festival once a year and to finance that we run (amongst other things) a bar once a year.

Music is still supplied by good old winamp! The nostalgia is strong.

Client: so how could we test this 😬
Me: you know what, send me an email at linuxxx@companyname.com and I can look if I can properly reply! Keep in mind though that this is for one time only, no further questions through that email address!
Client: Yes of course! *sends email*
Me: *tests* - *works fine* - *messages client back through the ticket system*
Client: *proceeds to send two follow up questions to my fucking work email address*

Me: *selects emails* - *marks emails as spam and deletes them*

Fucking seriously?! Cunt.

Improvise. Adapt. Overcome.

A group of wolves is called a pack.

A group of crows is called a murder.

A group of developers is called a merge conflict.

The topic of Alex Jones came up at work. In light of him getting banned from Apple, YouTube, Facebook etc: I'll leave this as I did around the office.

Linux desktop fanboys: proprietary hardware support is a huge issue in all major Linux distros. It is the fault of the hardware companies.

Also Linux desktop fanboys: hardware issues are the fault of the beginner/novice end user.

Windows/mac users: *installs any component they want and has it work flawlessly without even having to read a single word from the manual*

Me : I'm having a pretty bad headache.

Boss : Stop acting like a girl and get back to work.

Me: It's a migraine headache.

Boss: Ohh!! You know it's just in your head stop being a pussy. Don't think about the headache, and you won't feel any pain.

Me(in my head) : You fucking idiot you are partially correct it's in my head. But the pain won't stop if I stop thinking about it.

*Why the fuck does no one understand a neurological disease. If i'm not physically hurt, it doesn't mean i'm not in pain*

Fucking ignorant bastards.

*client calls in*

Me: good morning, how can I help you?
Client: my ip is blocked, could you unblock it for me?
Me: certainly! What's your ip address? Then I'll have a look.
Client: I'm not giving you my ip?! That's too privacy sensitive.
Me: 😶
Me: 😶
Me: 😶
Me: sir, I'm very keen on my privacy myself but without that information I can't do much for you 😬
Client: ah so you're refusing to help me?
Me: not like that, it's just very hard to lift an ip block for me when I don't know the ip address.
Client: you just don't want to help, fine.

*click*

😶

There WAS a time, when I was small, I made a Minecraft server , and asked my friends to join my server at 127.0.0.1

Gary's a prick

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 LIFE

The greatest phrase I ever heard..

After reading a lot of cryptography, I realized that it would be best if Alice and Bob just talk in person

Let's clarify:
* Github is not Git
* Android is not Java
* Unit test is not TDD
* Java is not OOP
* Docker is not Devops
* Jenkins is not CI
* Agile is not institutionalised total chaos
* Developer is not Printer Support

Being non-technical is not an excuse for being stupid

Infinite scroll in news websites should be banned.

@dfox could you update the app so it supports splitscreen?

http://motherfuckingwebsite.com/

Map, Filter and reduce explained!

404 stackoverflow.com Not Found

- Sleep 7h+ each night (you think you don't need it - but you do!)
- drink NO coffee (you've slept enough!)
- pair-up (you're not as good as you think)
- get a grasp on the problem (it's time will spent!)
- communicate constantly (you're not alonw especially)
- refactor just as much
- learn from you partner
- celebrate even small accomplishments (you need success!)
- go home and do something else (your pet project does not need more than 5hrs per week!)
- repeat (because repetition makes perfection!)

Hm.. so close..