this post was submitted on 26 Feb 2024
137 points (97.2% liked)

Programming

17528 readers
425 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 !webdev@programming.dev



founded 2 years ago
MODERATORS
 

As someone who spends time programming, I of course find myself in conversations with people who aren't as familiar with it. It doesn't happen all the time, but these discussions can lead to people coming up with some pretty wild misconceptions about what programming is and what programmers do.

  • I'm sure many of you have had similar experiences. So, I thought it would be interesting to ask.
you are viewing a single comment's thread
view the rest of the comments
[–] blazeknave@lemmy.world 3 points 9 months ago (5 children)

As a non-dev (tinker for fun) observer- it sounds like your friends and family think you're working in IT, but their assumptions thereafter are fair. Is that accurate? That the misconception is software dev does not equal IT?

[–] Buddahriffic@lemmy.world 5 points 9 months ago (2 children)

It goes a bit farther than that, even: IT work doesn't always equal IT work. Someone can be an expert in managing Linux-based load sharing servers and have no idea how to help a family member troubleshoot why their windows install is slow. Sure, they might have a better idea about how to start, but they'd be essentially starting from scratch for that specific problem rather than being able to apply any of their expertise to it.

Think of it like a programmer is a car builder, some IT people drive them for a living, others are mechanics. Someone who specializes in driving F1 cars might not have any idea why your car is rattling. The programmer might be able to figure it out if they built that car or the cause is something similar to what they see in the ones they have built. But if they build semis, odds are that isn't the case. But they might have a better idea than say a doctor.

[–] bootloop@lemmy.world 4 points 9 months ago

I use the medecine analogy: you wouldn't ask your dentist or even your GP to operate on your brain; doesn't mean that they are not good at what they do though.

load more comments (1 replies)
load more comments (3 replies)