this post was submitted on 22 Nov 2023
47 points (89.8% liked)
Programming
17314 readers
68 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, if I remember my software engineering prof correctly, software engineering is mostly about bringing an engineering mindset to software development. You wouldn't just slapdash an airplane together in a weekend and shove it out on the runway. There's a process for making sure we don't kill people with deadly flying contraptions.
Software engineering is that same idea applied to software systems. There is a process for making sure we do our job without causing undo harm. You wouldn't want to just slapdash together something that has to be HIPAA compliant and has to meet other security regulations. You plan. You test. You revise. You ensure the product doesn't publish the sensitive medical records of every patient on the front page before it ends up in production. That is the work of a software engineer.
To build upon this, we need to keep in mind that at least in some jurisdictions the role of a certified engineer is only required in projects with relevant size, and the responsibility of that engineer is to ensure the project complies with all requirements and therefore be held responsible for any mishap. This means that it's perfectly fine if non-engineers work independently on complex tasks, provided that an engineer attests that their output is fine and takes responsibility in case it isn't and it causes problems.
I really like this answer, because now I'm confident that I'm at least acting as an engineer. Thanks!