189

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.
(page 2) 50 comments
sorted by: hot top controversial new old
[-] 0x0@programming.dev 19 points 8 months ago

That you can mix and match bugfixes like lego blocks an hour before release.

[-] CoggyMcFee@lemmy.world 13 points 8 months ago
load more comments (2 replies)
[-] anzo@programming.dev 11 points 8 months ago

Just 2 days ago some friends thought that I could get any job from the huge pool of available jobs out there...

[-] sirico@feddit.uk 11 points 8 months ago

That I'm in any way smart or good at math

[-] Snapz@lemmy.world 10 points 8 months ago

The files are IN the computer.

[-] iknowitwheniseeit@lemmynsfw.com 10 points 8 months ago

I was at a party explaining that we were finishing up a release trying to decide which bugs were critical to fix. The person that I was talking to was shocked that we would release software with known bugs.

When I explained that all software has bugs, known bugs, he didn't believe me.

[-] blazeknave@lemmy.world 9 points 8 months ago

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 17 points 8 months ago

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 15 points 8 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 (1 replies)
load more comments (2 replies)
load more comments
view more: ‹ prev next ›
this post was submitted on 26 Feb 2024
189 points (95.7% liked)

Programming

17314 readers
153 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 1 year ago
MODERATORS