this post was submitted on 15 Jun 2023
114 points (98.3% liked)

Programming

17028 readers
241 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
114
Programming and Humility (programming.dev)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

This is something I’ve been wondering about for a long time. Programming is an activity that makes you face your own fallibility all the time. You write some code, compile it or run it, and then 80% of the time, it doesn’t work exactly the way you imagined. There’s an error message, or it just behaves incorrectly. Then you need to iterate on it and fix the issues until you get the desired result, and even then it’s subtly wrong, and causes an outage at 3am on Sunday.

I thought this experience would teach programmers to be the humblest people in the world.

I can’t believe how wrong I was. Programmers can be the most arrogant dickheads you will ever meet. Why is that?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 year ago* (last edited 1 year ago)

I've seen variations of this opinion a lot in tech, but you don't have to sacrifice frank feedback to be a little more polite. Like sure "this code is dumb" is better than "you are dumb", but not as good as "this could be more efficient if we did y instead"

The latter is more helpful and less confrontational. The best devs I've worked with have been excited about code, and that came through in review. When they saw something that was wrong their feedback came across as excited to share rather than affronted by ignorance.

The thing devs don't like to admit is that a ton of stuff we argue about is more taste than science. There's no right answer to the classic performance vs readability thing, or where exactly the line is for effort vs payoff. Couching feedback around things like that a opinion often makes people way more receptive to it. "Hey I'd prefer if we did it this way" often goes a long way, IMO.