6 ms·
> "It's not a video games major." If it was true in the 80s, it was certainly true in the early 2000s when I was getting my CprE degree. I met quite a few peo
by Syonyk 5y ago
> "It's not a video games major."
If it was true in the 80s, it was certainly true in the early 2000s when I was getting my CprE degree. I met quite a few people who were studying ComS or CprE for reasons that can be summed up as, "I built my own computer, I like video games, people said I'm good with computers, so I should be a Computer Science/Computer Engineering major!" They rarely lasted more than a semester or two, though I think the most epic flameout I knew managed a whopping 0.34 GPA his first semester...
And if the goal is "Get a degree, coast on through life with the easy money from computers," well... good luck. There are some very wide open pathways where if you're good, you can make lots of coin, but they're rare, and most tend to involve an awful lot of years of hard learning before you're competent (embedded dev and firmware/OS dev are some fields desperate for competent hires).
If you can write solid C, ring 0/EL3 doesn't scare you off, or you can figure out how to cram 10 pounds of hard realtime code into a 5 pound microcontroller... yeah, you'll go far. Come out having done the minimum, knowing Python and Javascript, well... there's an awful lot of competition for most of those positions if you're just a basic coder, not skilled at using those to accomplish interesting real world tasks ("make those images slide across the webpage" is not particularly novel or interesting anymore).
I'm struggling a bit to find ComS majors as a percent of degrees, but some stuff I've found indicates it's only in the 3-4% range or so today, so while it's double the percentage referenced in the article, it's not an order of magnitude higher by ratio (though in terms of degrees issued, probably, with college being more popular).
- nickysielicki 5y ago> If you can write solid C, ring 0/EL3 doesn't scare you off, or you can figure out how to cram 10 pounds of hard realtime code into a 5 pound microcontroller... yeah, you'll go far. Come out having done the minimum, knowing Python and Javascript, well... there's an awful lot of competition for most of those positions if you're just a basic coder, not skilled at using those to accomplish interesting real world tasks ("make those images slide across the webpage" is not particularly novel or interesting anymore). Go take a look at salaries and get back to me. Embedded does not pay as well as React/Rails, for the sole reason that React/Rails developers are closer to business problems.
- deleted 5y ago[deleted]
- theshadowknows 5y agoYou’re absolutely correct. I can write solid C :) but I make ok salary (155 base) and the vast majority of my work is doing architecture diagrams and writing reference code, most often in js. I also write a lot of sql.
- ThrowawayR2 5y ago"Past performance is not a predictor of future results". The gravy train might keep going for as much as another decade but, as more and more people are flooding into web development every year, at some point demand is going to be saturated and then ...
- joelbluminator 5y agoThere are also way more web jobs than embedded though, but you're right that another .com bubble will be bad for web devs (especially juniors, the seniors should do fine).
- quicklime 5y agoIs being "closer to business problems" really the sole reason? Or even a big reason? From the numbers I've seen, DevOps people are the best paid of all types of developers, but they aren't closer to business problems than React/Rails devs. I think it has more to do with the fact that most embedded developers are working on niche platforms and niche problem domains, so they don't enjoy the same level of job mobility as React/rails devs, who in turn don't have as much mobility as a DevOps person. Moving companies is by far the easiest way to get a pay rise. Job mobility gives you more negotiating power, and thus a higher salary.
- lelanthran 5y ago> Is being "closer to business problems" really the sole reason? Or even a big reason? It's got to do with visibility. Those people more visible to the holders of the purse strings get paid more than those who aren't. The closer you are to the business side of things, the more visible you are to the profit line. Compensation is very closely tied to how visible the role is to the company profits and/or leaders. A highly skilled DBA who ensure the most profitable application's DB is up, running and tuned is less visible than the business major who uses QlickView to send reports to the CEO. Guess who has more leverage to ask for money. Sidenote: Skills have nothing to do with compensation. For a long time I used to feel guilty whenever I learned that I was making similar money to someone who was more skilled at my role than I was. Now I don't feel guilty at all if I find out I'm making more than that person, and this is because I realised that the HR head, who has few relevant skills and can viably be replaced by a mollusc, makes more than I do. I don't feel guilty making more than others anymore, because other people making more than me don't feel guilty about making more than me.
- whatshisface 5y agoThe pay people are getting with their basic Python skills still outstrips non-programming professions at the same level of experience by a large margin. I also would like to express some skepticism about the embedded development pay scale idea, because a lot of those jobs are at engineering-first firms that put software, and by extension programmers, last.
- the_only_law 5y ago> because a lot of those jobs are at engineering-first firms that put software, and by extension programmers, last. I may be wrong, but I’m also skeptical of ever applying to these sort of positions because I feel they’d likely carry other aspects of engineering firms like heavy credentialism. l.
- whatshisface 5y agoI don't mind the idea of applying, as long as you negotiate seriously.
- poorjohnmacafee 5y agoI agree that knowing only basic Python or JavaScript isn't that useful today. In the companies I've worked at we've never hired a fresh grad or career change person whose skillset was described as "basic Python skills." We've only hired if they have professional experience, a compelling portfolio, or show some exceptional talent for a junior level. I think this is the norm.
- geofft 5y agoI have an MIT degree with coursework in operating systems and a lot of ring 0 experience and my well-paying job has me writing Python and JavaScript. As far as I can tell I'd be taking a significant pay cut if I went into embedded dev. Supply is higher for "basic coders" but demand is also much higher. There are a whole lot of images that need to be slid across web pages; there aren't that many CPU architectures that need Linux ported to them.
- rejectedandsad 5y agoThis is correct. At a hedge fund (ostensibly one like HRT given the pedigree you mentioned) geofft makes on the order of $500-700k or more, unlike mere mortals like me that went to a state school that make just $200k. Of course, I didn’t take any embedded classes and got an A- in my C class so perhaps I deserve nothing to begin with.
- imtringued 5y agoSpeaking of hedgefunds. Those are unlikely to hire embedded software developers but they may need a lot of "basic coders" and they can afford to pay them a lot even if the job is simple.
- deleted 5y ago[deleted]
- vmception 5y agohedge funds are not uniform enough to have any predictable set of skill requirements some need a node js script, some swear by python because an area of computational finance has gathered around it, some swear by languages closer to the metal, some have use cases that are better off with low latency stacks, others dont some are modifying FPGAs, others have simply negotiated a payout from a court case and will teach you F to analyze a dataset faster if they need coders at all, they all mostly need some level of quicker analysis but not possible to predict what kind of coder a hedge fund will need
- jlokier 5y ago> you can make lots of coin, but they're rare, and most tend to involve an awful lot of years of hard learning before you're competent (embedded dev and firmware/OS dev are some fields desperate for competent hires). Embedded dev and firmware both seem to pay comparatively poorly, despite the expertise required to do it well. Last year I discussed a number of contracts in this area, and when I found how much was on offer, they were all distinctly low compared with other contracts. OS dev, I will grant you, can pay well, eg kernel development, graphics drivers, storage layers. I think that's driven by servers and mobile devices more than embedded. > If you can write solid C, ring 0/EL3 doesn't scare you off, or you can figure out how to cram 10 pounds of hard realtime code into a 5 pound microcontroller... yeah, you'll go far. Oh if only! Doing that stuff is fun. I think cramming hard realtime into microcontrollers is best kept for hobby time if "coin" is what you're after though. Perhaps it's different for big, serious controller projects (like say a Mars rover or satellite), but I think mostly, embedded/microcontroller type things seem to be paid closer to mid-level electronic engineering levels. I don't know why, because there's a lot of expertise involved, but electronic engineering seems to pay considerably less than software at the moment.
- killtimeatwork 5y ago> (embedded dev and firmware/OS dev are some fields desperate for competent hires). There's a Samsung R&D center in my country where they do very cool and tough stuff and they ARE desperate for hires - mostly because their salaries are a laughing stock of the entire city. Web and data/backend pay best and the "tough" fields are trying to get by on sub-web salaries.