This bothers me a little bit as well as an electrical engineer. Being an engineer generally means a shared body of knowledge. We all take a ton of calculus clas

This bothers me a little bit as well as an electrical engineer. Being an engineer generally means a shared body of knowledge. We all take a ton of calculus classes, and nearly everyone takes a circuits 101, thermodynamics 101, statics 101 (no not statistics), dynamics 101...etc before getting into core classes. I wouldn't ever call myself a mathematician or a physicist despite having some overlap. In the same manner, someone who either goes through a coding boot camp, gets a comp sci degree, or just reads some books and starts coding are not engineers. They're programmers/developers and one of them has the formal training of a computer scientist and can be called that too. I'm not being elitist, it's just about using the right term. Engineer has meant something else for generations and overloading it doesn't help when they don't mean the same thing. As far as software engineering goes, I'd have to look into it some more. If they also take some of the same root classes (Ex: circuits, calculus, thermo, dynamics, statics, material balances...etc) and then just focus on software, I'd be ok with sharing the title of engineer as they truly do have the same heritage.