Today we interviewed a _very_ good Angular1 Dev, by chance we showed him the forked ngRouter module we use, after some debate he explained that we were using it incorrectly.. I asked if he'd used it before to which he responded:

"Yeah, I'm the guy who built it"

😅

"Whenever I see a door that says push I pull first to prevent conflicts"

"So, why do you want to work at our office in mexico?"
"I want to be a señor developer."

Every programmers dream convo

Programmers of today are like the monks of the middle ages. We use a language that people don't understand, we spend all our time sitting in a room reading, and people constantly ask us for advice but never really listens to the answer.

WHEN YOU DON’T LISTEN TO THE PROGRAMMER...

My GF just selected all files on her harddrive and clicked "Open".

The look at her face when she figured out what she have done.

BONUS: She restarts her computer, and upon start she selects Yes to the "Your computer shutdown unexpected, would you like to re-open the applications" popup 😂

🎂 happy birthday Linux!

I really need this t-shirt 👕

True that.!

Thank God they named it DevRant, not BitchBucket

if you want it done that way then fucking do it yourself because that shit makes no sense to me, and you have not adequately made your case to me as to why it makes sense, and since I'm writing it it seems prudent for it to make goddamn sense to me.

//The Lucky Bug

I am not anti-social, I'm just not client-friendly.

You know you're backend when it took you 30 minutes to program the inner workings of the platform... and 4 days to make it look pretty.

Pun of decade

Beer glass for programmers.. I need that 😂

Its not a bug

I went to Paris for my first interview (that was 1989) for a job of Unix kernel developer. All dressed up. I step out of the elevator and see a young punk with scruffy hair and different colour shoes. I reckon he must be the pizza delivery guy. I ask him "dude, can you please point me to the CEO's office for interview". He said "sure, follow me man, I'll show you". We arrive at a desk, he sat down in the big chair and looks at me with a big smile and says "Ok dude, here we are. I am the CEO. Now let's see how good you are!"
I got the job. And 26 years latet, last week, amazing coincidence: I met him again at a trade show in Paris ... with the same coloured shoes. How cool is that!!!

Developers who writes something similar

if (count >= 0) { return true; }

else { return false; }

deserves a special room in hell.

My mom once called me telling me her internet was not working. Prankster me told her that the whole internet closed at 7 pm. She was like "okay, I'll wait until tomorrow morning then" (it was around 8pm)
I couldn't help laughing like crazy as I didn't expect her to believe me.
Of course I helped her out so that she could have her game of poker. (She won $10.000 that night) :-)

Pointy Haired Boss: "There's an issue with this simple bit of that service, could you take a look?"
Me: "Sure, give me a minute to investigate"
*A minute later*
Me: "No wonder there's a problem, this code is horrendous! What idiot wrote this unmaintainable crap?"
PHB: "Doesn't matter, just fix it, test it and release it."
Me: "I just want to check who did it, so they never touch our code again."
*Checks SVN log*
Me: "Well, I guess I can never touch our code again."

Me: *coding*
Gf: *walks into room*
Gf: awww look at all the sad winky faces
Me: excuse me?
Gf: look at all the sad winky faces *points at this ); *
Me: ... 😕😂

Why computers are like men:

1. In order to get their attention, you have to turn them on.
2. They have a lot of data, but are still clueless.
3. They are supposed to help you solve problems, but half the time they are the problem.
4. As soon as you commit to one, you realize that if you had waited a little longer, you could have had a better model.

Why computers are like women:

1. No one but the Creator understands their internal logic.
2. The native language they use to communicate with other computers is incomprehensible to everyone else.
3. Even your smallest mistakes are stored in long-term memory for later retrieval.
4. As soon as you make a commitment to one, you find yourself spending half your paycheck on accessories for it.

cuting edge ux

You know you've succeeded as a parent/programmer when your kids start counting up from 0.

so true!!

One of our web developers reported a bug with my image api that shrunk large images to a thumbnail size. Basically looked like this img = ResizeImage(largeImage, 50); // shrink the image by 50%
The 'bug' was when he was passed in the thumbnail image and requesting a 300% increase, and the image was too pixelated.
I tried to explain that if you need the larger image, use the image from disk (since the images were already sized optimally for display) and the api was just for resizing downward.
Thinking I was done, the next day I was called into a large conference room with the company vice-president, two of the web-dev managers, and several of the web developers.
VP: "I received an alarming email saying you refused to fix that bug in your code. Is that correct?"
Me: "Bug? No, there is no bug. The image api is executing just as it is supposed to."
MGR1: "Uh...no it isn't. Images using *your* code is pixelated and unfit for our site and our customers."
MGR2: "Yes, I looked at your code and don't understand what the big deal is. Looks like a simple fix."
<web developers nodding their heads>
Me: "OK, I'll bite. What is the simple fix?"
<MGR2 looks over at one of the devs>
Dev1: "Well, for example, if we request an image resize of 300, and the image is only 50x50, only increase the size by 10. Maybe 15."
Me: "Wow..OK. So what if the image is, for example, 640x480?"
MGR1: "75. Maybe 80 if it's a picture of boots."
VP: "Oh yes, boots. We need good pictures of boots."
Me: "I'm not exactly sure how to break this to you, but my code doesn't do 'maybe'. I mean, you have the image from disk.
You obviously used the api to create the thumbnail, but are trying to use the thumbnail to go back to the regular size. Why not use the original image?"
<Web-Dev managers look awkwardly towards the web devs>
Dev3: "Yea, well uh...um...that would require us to create a variable or something to store the original image. The place in the code where we need the regular image, it's easier to call your method."
Me: "Um, not really. You still have to resolve the product name from the URL path. Deriving the original file name is what you are doing already. Just do the same thing in your part of the code."
Dev2: "But we'd have to change our code"
Mgr2: "I know..I know. How about if we, for example, send you 12345.jpg and request a resize greater than 100, you go to disk and look for that image?"
<VP, mgrs, and devs nod happily>
Me: "Um, no that won't work. All I see is the image stream. I have no idea what file is and the api shouldn't be guessing, going to disk or anything like that."
Dev1: "What if we pass you the file name?"
<VP, mgrs, and devs nod happily again>
Me: "No, that would break the API contract and ...uh..wait...I'm familiar with your code. How about I make the change? I'm pretty sure I'll only have to change one method"
VP: "What! No...it’s gotta be more than that. Our site is huge."
<Mgrs and devs grumble and shift around in their chairs>
Me: "I'm done talking about this. I can change your code for you or you can do it. There is no bug and I'm not changing the api because you can't use it correctly."

Later I discovered they stopped using the resize api and wrote dynamic html to 'resize' the images on the client (download the 5+ meg images, and use the length and width properties)

My job is so f**king unbelievable.

I'll try to sum it up by first telling you about the folks I work with:

First, there is this supermodel wanna-be chick. Yeah, okay, she is pretty hot, but damn is she completely useless.
The girl is constantly fixing her hair or putting on make-up.
She is extremely self-centred and has never once considered the needs or wants of anyone but herself.
She is as dumb as a box of rocks, and I still find it surprising that she has enough brain power to continue to breathe.

The next chick is completely the opposite. She might even be one of the smartest people on the planet.
Her career opportunities are endless, and yet she is here with us. She is a zero on a scale of 1 to 10.
I'm not sure she even showers, much less shaves her "womanly" parts.
I think she might be a lesbian, because every time we drive by the hardware store she moans like a cat in heat.

But the jewel of the crowd has got to be the fucking stoner. And this guy is more than just your average pothead.
In fact, he is baked before he comes to work, during work, and I'm sure after work.
He probably hasn't been sober any time in the last ten years, and he's only 22.
He dresses like a beatnik throwback from the 1960's, and to make things worse, he brings his big f**king dog to work.
Every f**king day I have to look at this huge Great Dane walk around half-stoned from the second-hand smoke.
Hell, sometimes I even think it's trying to talk with its constant bellowing.
Also, both of them are constantly hungry, requiring multiple stops to McDonald's and Burger King, every single f**king day.

Anyway, I drive these dicks around in my van and we solve mysteries and s**t.

'this' in JavaScript

Enough said :|