many of these roles could be accomplished by people who have non university qualifications or 4-5 year apprenticeships. But it’s hard to teach the background maths involved during an apprenticeship
This was a very interesting example. Personally, I don't use any of the higher math that degree programs wanted. For people in the field you're talking about, it would be needed. So in that sense, a dev working for one company would be fine, until they wanted to dev for a company that needs those maths.
I counter my own point though and say that most people who don't use those higher level maths forget it. I am a very good use or lose example.
@cole@cole@lemdro.id I agree there can be separation of role types. This is annoyingly inconsistent across industry. Lead/architect/principle/engineer terms get thrown around for all kinds of roles. Sometimes companies just use them as title changes for promotion and talent retention. It would be nice if companies considered adapting a standardize framework for some uniformity. The NICE model comes to mind, but I've had people tell me they think it's too academic and not pragmatic in the real word. I don't think I agree with them.