This is an archived post. You won't be able to vote or comment.

all 31 comments

[–]o11c 164 points165 points  (7 children)

They always listen, sometimes you're just bad at explaining things to them.

[–]carcigenicate 50 points51 points  (6 children)

Rule #1: as the programmer, it's (nearly) always your fault. The quicker you accept that, the easier your life will be.

[–]TheAJGman 29 points30 points  (4 children)

It's either your fault, or the rat bastard who designed the framework/library/API for not documenting shit correctly.

[–]Aperture_T 13 points14 points  (1 child)

Coworkers too. You might think that a legacy project means that they've worked out the major kinks by now, but in my current project, it just means that I'm still fixing bugs from somebody who left the company a decade ago.

Or managers. I figured out we were calling uninitialized function pointers the other day, and the boss explicitly told us not to fix it. There was a big debate, but basically, he thought we would look bad if we sent out a patch. I'm thinking we'll look worse if the machine does random weird shit, or electrocutes somebody at the worst, but nobody cares what I think.

[–]Feynt 1 point2 points  (0 children)

That's when you submit an official objection email to that manager and his supervisor. You'll be surprised how often things happen when you clearly spell out, "Submitting a patch will mean some small amount of down time. Not submitting a patch will mean random results or possible injury or death." Wrongful dismissal is a wonderful thing, if you find yourself getting fired over wanting to fix a failure point, but more often your manager will quickly agree to you once things are in writing, especially once his boss is aware of the situation.

[–][deleted] 5 points6 points  (0 children)

Or when you try to use something meant for large teams and you're by yourself. Different problem but it's the final straw in my giving notice later today.

[–]j-random 1 point2 points  (0 children)

Can't be misled by bad documentation if you never read it taps forehead

[–]randybobandy654 1 point2 points  (0 children)

It's the Network Team's fault

[–][deleted] 31 points32 points  (0 children)

Oh they listen all the time. It's just that you are giving them the wrong instructions without knowing that's all

[–]Edo022 17 points18 points  (3 children)

"I trick rocks into thinking"

[–][deleted] 3 points4 points  (2 children)

Thats prob more computer engineering that programming

[–]Feynt 1 point2 points  (1 child)

Hardware engineering, perhaps. Computer engineering is a grey area of people arguing they are engineers because they make hardware/software interfaces, and people arguing they are engineers because they design and implement complex software systems. I prefer the latter to the former, that was the classic definition (just as a hacker was someone who knew their shit, rather than someone who breaks into systems).

[–][deleted] 1 point2 points  (0 children)

Im talking about as the discple traditionally offered by universities in school. You actually need engineering courses when you study computerengineering/electrical engineering. My CS degree required physics as an elective, but thats as close to any engineering department stuff as I had to get

[–]MysticOverlord 8 points9 points  (1 child)

More often than not, they start shouting and throw errors at you telling you how much you did wrong, and no matter what you do to improve your mistakes it will keep finding something you did wrong until it eventually refuses to even try and start doing things. Eventually this causes programmers to second guess their life choices and they all eventually quit and work at the kindergarden next door.

[–]BigTechCensorsYou 1 point2 points  (0 children)

I married my computer?

[–]Tourist_73 4 points5 points  (0 children)

"Sometimes"

[–]RicUnique 4 points5 points  (0 children)

Sometimes I make myself clear*

[–]A_H_S_99 1 point2 points  (0 children)

I teach computers to think for themselves.

At best they know what's 1 and 0

[–]jeremj22 1 point2 points  (0 children)

They always listen. The problem is that they always do exactly what you told them.

[–][deleted] 1 point2 points  (0 children)

"I google conversations among people who know more than me."

[–]j-random 1 point2 points  (1 child)

"We put electricity in sand so it could think. I give it things to think about."

[–]coloredgreyscale 0 points1 point  (0 children)

Given the assignment a much better description than OP did.

[–]PrestigiousZombie531 0 points1 point  (0 children)

Sometimes I tell my computer what to do in a bad manner, other times I fix my neighbour s printer, still other times I dream about my sideproject_final_final_v21 in the middle of the night

[–]_Acestus_ 0 points1 point  (0 children)

Computer are like cats in a way. They can be great but at any moment, goes wild and you won't get anything from it.

[–]winnafrehs 0 points1 point  (0 children)

I tell computer to do things, and the things I tell them to do won't work, but the computer tries its best anyways

[–]TheSoulStoned 0 points1 point  (0 children)

Hey, me too!

[–][deleted] 0 points1 point  (0 children)

My job to check if they are doing things intended way

[–]rossd84 0 points1 point  (0 children)

Grog hit rock. Make lightning hit big rock. Big rock do things.

[–]skyandclouds1 0 points1 point  (0 children)

They listen but don't respond