4 ms·
>What defines academic here? The author is not a professor nor a phd in CS as far as I can tell. True - I did not realize that. But what I mean by academic is
by BeetleB 10y ago
>What defines academic here? The author is not a professor nor a phd in CS as far as I can tell.
True - I did not realize that. But what I mean by academic is someone who is not in industry and mostly has teaching or research experience.
>I would argue this list is more broad than an academic would write necessarily.
Pretty much everything listed is part of the CS curriculum - either as a required course or as an elective.
>But I argue a lot of the new technology-driving things that are made, are not made by Type 2 engineers as well. I would argue many of the new "wow" things that are coming forward in tech require a quite strong Type 1 background - similar if you're trying to work in finance. E.g. Alexa the device alone requires a lot of hw, os, fs, nlp, ai, networking work.
No disagreement here. But how easy is it to get a job in these even if you have a Type 1 background?
It's the same story in other disciplines, like my own background in physics/electrical engineering. When looking for a job that utilized the skills I had learned, I found very few. Most listed a minimum of a PhD (even if the job really didn't need that much knowledge), which I didn't have as I dropped out of my PhD program. What's more, once I was "inside" with a job, I found out most people doing jobs that required a PhD were doing work that required even less technical skills than the job I was doing (and my job required knowledge of one somewhat advanced topic, but no heavy mathematics).
Yes, I accept the jobs you write about exist. But it is hard to get them even when you have the skills. The supply vastly exceeds the demand. So why spend time honing these skills (beyond personal curiosity)?
>But even at a google/fb/amazon/microsoft there are opportunities for type 1 work. At Apple for example there is the Core OS and Networking Teams. At Google there are quite a few OS, networking, SDN, algo, distributed sys, file store, ...etc teams.
Same is true at the large company I work in. And again, the majority of software jobs at my company are Type 2.
>And in terms of core skills I would argue there are people who get paid /quite a bit/ more for their abilities.
My argument is not that these people do not exist. My argument is that when you look at the typical person who has Type 2 knowledge, they are not paid that much more (I suspect it is true even when restricting to jobs that need that knowledge).
Look at web development. I know some people really get paid a lot for it. But most of the people I know in it who do network programming (and not trivial network programming) get paid less than I do. And my salary is not high. The web is a particularly notable example. I routinely bump into software developers doing web work that requires a lot more ingenuity than my boring business logic work. Few get paid more than me.