this post was submitted on 22 Nov 2023
46 points (89.7% liked)
Programming
17398 readers
150 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
Considering the almost complete lack of standards, certification, licensing in most areas of programming, I don't think there's a ton of difference.
I've held both titles without rhyme or reason between the two. Even in areas requiring high compliance - HIPAA, PCI/DSS, NIST Standards, FERPA, etc - training achieved doesn't tend to be reflected in a programmer's title. (Even while the same level of training turns into acronym soup among their IT peers.)
One way I try to live up to the title "Engineer" - even when I don't wear it - is by holding myself to the Engineering Code of Ethics.
One of the issues is that devs don’t know about the normal engineering certifying body (at least in the US). One of the problems with that body was its expectation that a software engineer also know other forms of engineering. For example, a chemical engineer needs to know some civil and industrial engineering to get their certification. It’s almost nonsensical to ask someone building cloud apps to understand the principles of chemical engineering unless their work is in chemical engineering.
I know a ton of engineers that don’t view software as a field that can use the term because of its lack of certification.
Superb for including the Engineering Code of Ethics which I didn't know exsisted! In my decades of working on every part of Computer Systems, Information Systems, unfortunately, I personally think if you work for Big Tech, you cannot abide those Code of Ethics. From the website>
Fundamental Canons
Engineers, in the fulfillment of their professional duties, shall:
How many Google Code Monkeys violate 1 or more of those on the daily? For instance in Canon 1, it does not say profit is paramount, but that public welfare is paramount. In fact, you could argue that is a competing objective working for Big Tech and following ethics.