And to say the truth, it’s all just part of the game. 12 years ago I called myself programmer or web developer. But when the industry popularized the term Software Engineer, I went with that, because in the end I wanted to be hired, rather than dealing with semantics of the word “engineer”.

FWIW, your bullshit title is just as bullshit as everyone else's bullshit title. It's what you do that matters. Most programmers / software developers / software engineers are garbage at their job, and I give it about a 0% chance that your accredited software engineering degree means you're any less likely to be garbage too. The guys who walk around talking about how they have a Bona Fide Microsoft Partner Certification (BFMPC) are usually the worst coders of all. You realize that they literally just called it "Engineering", right? Some universities call it "Engineering" and some don't, that's just a word they decided to use. You're literally claiming to be better than other people because your college called it "Engineering" instead of "Science". That's the kind of person you're deciding to be.

Anyone can get through school; it's meaningless. And it's meaningless that your college happened to pick the word "Engineering" for your degree. My local colleges distinguish between "computer engineering" and "computer science" as the former being more focused on logic gates and C, and the latter being more focused on type theory and high-level programming languages. That's all it is -- a focus.

The only titles that matter are those that can be revoked, like a medical license, the Bar Association, or a Professional Engineer's license (which is not the same as simply having graduated with the word "Engineering" in your degree), because at least then you know the person is less likely to be literally dangerously unqualified. But I'm guessing your Superior Better-Than-Everyone-Else Bachelor of Software Engineering Accredited by the Australian Institute of Engineers isn't something they'd revoke if it turned out you didn't know a for-loop from your own asshole, is it?

I would argue that engineering isn't certifications, exams, or education. Those are methods of quality control, not the act itself.

Merriam-Webster gives the following definition for engineering:

> 1: the activities or function of an engineer

> 2a: the application of science and mathematics by which the properties of matter and the sources of energy in nature are made useful to people

> 2b: the design and manufacture of complex products software engineering

> 3: calculated manipulation or direction (as of behavior) social engineering compare genetic engineering

(https://www.merriam-webster.com/dictionary/engineering)

The first definition is unhelpful as it takes us back to the question of definition, but definitions 2-3 apply to software engineering.

Should software engineering require the same quality control mechanisms as civil or mechanical engineering? Possibly, but that's a very different question.