[adamdb]

I once had an argument with a close friend of mine while earning her PHD in a non-computer engineering field. It was about the semantics of "Computer Engineering" and "Software Engineering", or any variant involving computers. Her argument was that every (virtually, I think?) other engineering discipline requires a certificate after graduation to ensure their competency. Every since then I've also argued for similar industry standard certifications for Computer and Software Engineers. I was a hiring manager for over a decade at a well known MNC, so I can attest that this doesn't, or didn't exist (since the global mass-layoff). I tried to improve interview standards in the past and help establish some forward momentum, but pulling-the-ladder-up and biased-hiring-practices have made this even more elusive.

Edit: I know there are some certifications that may be required by some software engineers, computer engineers, etc. But this is limited to critical/near-failure-proof systems. Which I willing to wager is less than 1% of those employed in these fields.

[rererereferred]

There was one teacher/dean who was adamant at getting the career out of the "engineering" area at my country's universities and that "Software Engineering" should not exist as a career.

One funny interaction I remember, MariaDB's Monty came to give a talk and he asked "If one wants to help with MariaDB should they be a software engineer or a computer scientist?" Monty's answer was "you just need to know C."