Slashdot Mirror
Electrical Engineering Employment Declines Nearly 10%, But Developers Up 12%
dcblogs writes The number of people working as electrical engineers declined by 29,000 last year, continuing a long-standing trend, according to government data. But the number of software developers, the largest IT occupational category, increased by nearly 12%,or a gain of 132,000 jobs. There were 1.235 million people working as software developers last year, and 271,000 electrical engineers, according U.S. Bureau of Labor Statistics data.
Let's be honest about this. Electrical engineering can now be outsourced fully, as companies do not see the value in EE or more importantly that the skills are transferable to other areas such as programming. Furthermore, ageism is rampant in most of the technical field now, as HR types will want to hire someone their own age.
I'm an electrical engineer myself and the BLS statistics for this profession are misleading. The government categorizes electrical engineers into several sub-categories: electronic engineers, electrical engineers, fabrication engineers (silicon folks) and there is another for power engineers (the guys who work for the power company). I'd be hesitant to take this headline seriously without looking into it further.
15-20 years ago there were plenty of manufacturing jobs for EE's. It was a great way to learn how things were really put together, and in many cases it was the foundation of a good design engineering career. Places like HP/Agilent did a lot of their test an measurement RF/microwave career paths this way. A few years of keeping a production line that making RF/microwave widgets was a great way to learn the ropes and see how to (or not) make a good manufacturable design. Virtually all of that type of work is now offshored to Malaysia, China, and similar.
Much of the design work has been eaten up by better ADC's and DAC with gobs of FPGA's doing what used to be an art form. So now the minimum level of skill needed to work as a decently paid EE doing actual EE work is very very high.
Large numbers lost their jobs as the manufacturing went elsewhere and the engineers scurried to other jobs like programming, IT, etc to be able to feed themselves. There is a vacuum now between the EE graduates and the companies who need to hire more EE's. Companies want 5 years experience minimum to make sure you aren't a buffoon (and because they often simply have no entry level work to do), but there are very few entry level jobs to get that experience. So lots of fresh graduates find other work outside their EE degree. So lots of graduates, lots of job openings, and no good way to span the apprenticeship gap.
In real production code these days, "maintainable code" is what matters. Sure, on very rare occasions you'll google some algorithm you vaguely remember form college that's not already in your library, but most code just isn't performance sensitive (in an algorithmic sense) or even algorithmically interesting.
What matters is living with that code for many years after writing it, and not hating life. And that is still as much art as science. Sure, best practices continue to be formalized, but the field is still young in that respect, and I don't expect maintainability to settle down into "a set of rules to follow" before my career ends.
Socialism: a lie told by totalitarians and believed by fools.