Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Software engineers don't really -- well, in the US anyway, might differ elsewhere -- have a formal accreditation process, which I understand is common in other areas of engineering and is a bit of a point of friction with people in some other fields. Like, you don't get to just roll up and say "I'm a civil engineer and I'm building a bridge now" the way you can a software engineer writing a software package.
I don't especially think that such a process would be incredibly practical, but...shrugs
I can't speak for other engineering trades or even other software degrees from other universities but I know my degree was ABET accredited (US) for what it's worth. A massive chunk of our education was instilling the engineer's mindset in terms of architecture, design, test-driven, development QA/QC, and coordination and integration with other specialties in the system. I really do wish there was a protection over the title, for I agree some may call themselves software engineers but were never actually trained in the engineering design process.
I'm an electrical engineer, and I've always considered any field where your design work makes you directly liable for the safety/well-being of others earns you the title of "Engineer".
"Engineering" as a verb is something most anyone can do. Working to understand a problem and then developing a solution is a universal joy for people of any age and skill.