The actual laws vary country to country. Canada has the strictest laws, where everybody called an "engineer" needs a license. But in most places, only the "principle engineer", the one who signs off on plans, needs a license. The people under them don't.
-
-
I think the use of titles like "SRE" and "DevOps" like is part of this. What do you call an engineer you hire to operate a large system? In EE or ME, they might be a tech. But "tech" is low prestige, low pay, etc., inventing a different name for the same job is a way around that
-
This comment isn't meant to throw shade at techs or SREs, I don't think EE techs have jobs that require less skill than EEs, but the classical career paths look a lot worse in terms of pay, advancement, etc., because it's considered lower class.
- 1 more reply
New conversation -
-
-
even with the illustration of "electrical engineer" vs "electrician", I'm not sure what the supposed division in the case of software between "engineer" and "developer" is supposed to be in the first place, *especially* in light of the *first* tweets in the thread …
-
much day-to-day engineering work is humdrum in the way I gather a "developer's" would be. If you want to preserve "engineer" at all, why isn't the CRUD writer's work like that of the person working on the suitcase?
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.