this post was submitted on 27 Mar 2025
505 points (99.2% liked)

Programmer Humor

22219 readers
1853 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 41 points 1 week ago (2 children)

This is just a meme, but I find that communication is an underrated skill among software engineers.

Personally, I'm trying to get better at it.

[–] [email protected] 20 points 1 week ago (1 children)

I find that communication is an underrated skill among software engineers

The problem, which is sometimes too common, is if they have too good communication skills combined with lacking technical skills. These are the ones that BS their way up the ladder, while screwing over the people that count on them, because their code sucks (the actual important part, for a SW engineer).

But yeah if you're both good technically and a communicator, you're pretty damn valuable. Personally, I'd be willing to muscle through terrible comm skills if the technical talent that matters was there.

[–] [email protected] 11 points 1 week ago (2 children)

I’m what you describe: my technical skills aren’t top notch but I communicate well. But I don’t bullshit my way up any ladders, but try and do what I do best; that is, facilitate the communication between people who might not be able to communicate with each other.

Not many in my teams could put a finger on what exactly I did, but all agreed I was fairly valuable and things became worse when I left.

[–] [email protected] 3 points 1 week ago

Were you a people person, dammit

[–] [email protected] 2 points 1 week ago

Not many in my teams could put a finger on what exactly I did, but all agreed I was fairly valuable and things became worse when I left.

See: Being Glue

[–] [email protected] 5 points 1 week ago

it's about over analyzing your current tasks and over describing common minutiae.

instead of: "I worked on restoring a database connection"

it becomes: "I worked with the DBAs, networking, and OpSec to restore the connection and ensure that connectivity remains up and secure. I also plan on working on adding proper monitoring to alert when this happens again. I should be done in a few days."

then in a few days it becomes: "ran into scheduling conflicts with the monitoring team and will need it push it out until next week. Until then I'll continue the monitor the situation and let you know if anything new comes up."