Based on some places I used to work, upper management seemed convinced that the "idea" stage was the hardest and most important part of any project, and that the easy part is planning, gathering requirements, building, testing, changing, and maintaining custom business applications for needlessly complex and ever changing requirements.
this post was submitted on 26 Feb 2024
181 points (95.5% liked)
Programming
17313 readers
34 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
That you can mix and match bugfixes like lego blocks an hour before release.
That I'm in any way smart or good at math
Just 2 days ago some friends thought that I could get any job from the huge pool of available jobs out there...
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.
The files are IN the computer.
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?
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.
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)