A young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.

It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.

Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).

So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...

So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.

We'll see how this goes! Who the hell wants a toolbar anyway?!

when you have no QA department
- via CodeHumor

Client: Can I speak to the developer responsible for my website?
Developer: Speaking...
Client: You have a deep voice for a 5 year old.

A mechanical engineer, an electrical engineer, and a programmer are riding in a car.

The car breaks down and coasts to the side of the road.

"Hang on," says the mechanical engineer. "The problem is probably the engine, let me have a look at it and I'll have us on the road again in no time."

"Wait," says the electrical engineer. "The way it just stopped like that, I think it's the electrical system. Let me have a look and I'll get us going again in a minute or two."

"Hold on," says the computer engineer. "Why don't we all just get out of the car and get in again, and then see if it starts?"

Alternate punchlines:

"Why don't we open and close all the windows, and then see if it starts?"

"Why don't we remove parts from the engine until it starts successfully?"

I dream of having a garage.

*Reinstalls devrant
*Double taps some rants
DevRant: Dood did you know that you can DOUBLE TAP rants to updoot!?!

Classic

Sleep deprivation may have made this funnier than it actually is, but I can't NOT laugh when I see it

Source: Saturday Morning Breakfast Cereal (smbc)

Last day on my current job before switching to a new company.
I have 10 tasks on my "to finish before leaving" list.

Finished one task and showed it to my boss.

I now have 13 tasks on my "to finish before leaving" list.

Do you want to get people to quit? Because that's how you get people to quit.

Me: *staring at computer screen, not looking busy*

Boss: Why are you not working?

Me: I am, I'm just waiting for this thing to finish installing.

Boss: You do realize you can still do other stuff while that's running, right?

Me: Didn't you send me an article last week about the dangers of multitasking?

Boss: um...

Me: *now intently staring at progress bar..."

Boss: fuck sakes... *walks away*

Me: double taps a rant to upvote.

Popup: Hint. You can double tap a rant to upvote.

Umm, sure. Thanks..

thank god electrical engineers exist because fuck hardware

Christmas.
The only time where computer scientists and other people agree how trees are shaped.
Now we only need to convince them that the tip is in fact the root.

Me searching for some random ideas.

Case 1
Me - I want to create something.
Friend - Can you hack into ... ?
Me - No, bye

Case 2
Me - I want to create something.
Bro - I also want to create one awesome project
Me - Ok, cool

Case 3
Me - I want to create something
Mom - Come, help me with preparation for dinner.
Me - *I have been trapped* Nice move

LONG RANT AHEAD!

In my workplace (dev company) I am the only dev using Linux on my workstation. I joined project XX, a senior dev onboarded me. Downloaded the code, built the source, launched the app,.. BAM - an exception in catalina.out. ORM framework failed to map something.

mvn clean && mvn install

same thing happens again. I address this incident to sr dev and response is "well.... it works on my machine and has worked for all other devs. It must be your environment issue. Prolly linux is to blame?" So I spend another hour trying to dig up the bug. Narrowed it down to a single datamodel with ORM mapping annotation looking somewhat off. Fixed it.

mvn clean && mvn install

the app now works perfectly. Apparently this bug has been in the codebase for years and Windows used to mask it somehow w/o throwing an exception. God knows what undefined behaviour was happening in the background...

Months fly by and I'm invited to join another project. Sounds really cool! I get accesses, checkout the code, build it (after crossing the hell of VPNs on Linux). Run component 1/4 -- all goocy. run component 2,3/4 -- looks perfect. Run component 4/4 -- BAM: LinkageError. Turns out there is something wrong with OSGi dependencies as ClassLoader attempts to load the same class twice, from 2 different sources. Coworkers with Windows and MACs have never seen this kind of exception and lead dev replies with "I think you should use a normal environment for work rather than playing with your Linux". Wtf... It's java. Every env is "normal env" for JVM! I do some digging. One day passes by.. second one.. third.. the weekend.. The next Friday comes and I still haven't succeeded to launch component #4. Eventually I give up (since I cannot charge a client for a week I spent trying to set up my env) and walk away from that project. Ever since this LinkageError was always in my mind, for some reason I could not let it go. It was driving me CRAZY! So half a year passes by and one of the project devs gets a new MB pro. 2 days later I get a PM: "umm.. were you the one who used to get LinkageError while starting component #4 up?". You guys have NO IDEA how happy his message made me. I mean... I was frickin HIGH: all smiling, singing, even dancing behind my desk!! Apparently the guy had the same problem I did. Except he was familiar with the project quite well. It took 3 more days for him to figure out what was wrong and fix it. And it indeed was an error in the project -- not my "abnormal Linux env"! And again for some hell knows what reason Windows was masking a mistake in the codebase and not popping an error where it must have popped. Linux on the other hand found the error and crashed the app immediatelly so the product would not be shipped with God knows what bugs...

I do not mean to bring up a flame war or smth, but It's obvious I've kind of saved 2 projects from "undefined magical behaviour" by just using Linux. I guess what I really wanted to say is that no matter how good dev you are, whether you are a sr, lead or chief dev, if your coworker (let it be another sr or a jr dev) says he gets an error and YOU cannot figure out what the heck is wrong, you should not blame the dev or an environment w/o knowing it for a fact. If something is not working - figure out the WHATs and WHYs first. Analyze, compare data to other envs,... Not only you will help a new guy to join your team but also you'll learn something new. And in some cases something crucial, e.g. a serious messup in the codebase.