The way I see it, any time you are building a system, you're an engineer. Theoretical computer scientists aren't really building systems, they're uncovering the mathematical foundation for the work that we do, so they don't count as scientists.
In contrast, someone implementing algorithm, is by this definition, an engineer. A good algorithm necessarily needs you to get your hands dirty with the nitty-gritties of the system the algorithm is going exist in. So, these guys are engineers.
I also think the guys who are deciding our taxes, studying economic policies and government should all be considered as engineers because these folks area also building systems, with the caveat that these systems have human beings inside them.
Comments
The way I see it, any time you are building a system, you're an engineer. Theoretical computer scientists aren't really building systems, they're uncovering the mathematical foundation for the work that we do, so they don't count as scientists.
In contrast, someone implementing algorithm, is by this definition, an engineer. A good algorithm necessarily needs you to get your hands dirty with the nitty-gritties of the system the algorithm is going exist in. So, these guys are engineers.
I also think the guys who are deciding our taxes, studying economic policies and government should all be considered as engineers because these folks area also building systems, with the caveat that these systems have human beings inside them.
In some countries (and increasingly in the US), applied econ/finance/policy is considered a form of engineering - quite true.