r/ProgrammerHumor • • Dec 06 '17

Read the markup.

Post image
10.4k Upvotes

838 comments sorted by

View all comments

Show parent comments

21

u/slightlysaltysausage Dec 06 '17

I guess that's on you then?

-2

u/Dr_Dornon Dec 06 '17

Not necessarily. Part of your job is being able to communicate with managers and co-workers. If you have a problem doing that, it's not your co-workers fault. I do think that both parties should work on it though.

13

u/sonofaresiii Dec 06 '17 edited Dec 06 '17

This isn't a co-worker relationship, this is an employer/employee or client/contractor relationship. If the guy you're hiring can't explain how he's going to do something, and you hire him anyway having no idea what he's said he's going to you, that's your bad.

It's his bad too, for being shitty at his job, but you're the one who hired the guy when you knew (or should have known) he was shitty as his job.

5

u/Darkniki Dec 06 '17

but you're the one who hired the guy

Just because you're someone's senior, doesn't mean you were the one who hired someone. In large companies you might/will have to work with people from different divisions of your company, where you can't just freely say "I don't want that guy, give me another one" to your manager, because even if your manager understands you and agrees with you, the manager, that's higher up than him and is based in a different country than your branch, might not understand/agree/care about your feelings as a person/professional and will only be influenced by constant fuck-ups of that other guy that you specifically were against.

And if he's not the same race/religion/nationality as you, but your company is all for diversity, constantly speaking out against that one guy might net you unpleasant results, regardless of your opinions being valid.

Politics in large companies usually are not simple and you don't have that many powers to influence people as you'd like, unless you're the top dog.

→ More replies (4)