Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Programming Stats Technology

Software Development Employment Rises 45% In 10 Years 118

dcblogs writes "Software employment is rising at 4 to 5% a year, and may be the only tech occupation to have recovered to full employment since the recession. Other tech occupations aren't doing as well. In 2001, there were more than 200,000 people working in the semi-conductor industry. That number was less than 100,000 by 2010, according to a recent study by the Economic Policy Institute. Darin Wedel, who was laid off from Texas Instruments, and gained national attention when his wife, Jennifer, challenged President Obama on H-1B use, said that for electrical engineers, 'unless you are in the actual design of circuits, then you're not in demand.' He said that much of the job loss in the field is due to the closing of fabrication facilities. Wedel has since found new work as a quality engineer."
This discussion has been archived. No new comments can be posted.

Software Development Employment Rises 45% In 10 Years

Comments Filter:
  • Tech bubble (Score:4, Interesting)

    by internerdj ( 1319281 ) on Tuesday July 23, 2013 @10:39AM (#44360907)
    I'm curious, what does the data look like for 12 or 15 or 20 years?
  • by Joining Yet Again ( 2992179 ) on Tuesday July 23, 2013 @10:43AM (#44360935)

    I always thought it was about EE requiring a *different* mindset rather than "more talent". There are lots of "run of the mill" EE jobs too, which don't require the full gamut of skills learnt e.g. during your degree programme - just as most software jobs won't require most of what you learnt at school.

    My academic background is in mathematics. I found anything from the purest mathematics to the underlying physics relevant to EEs a lot easier that did the EEs I bumped into, yet I find circuit study entirely unintuitive. I keep thinking that I'm missing something when trying to design/troubleshoot some electronics (always merely for fun). Even something as simple as the various designs for an oscillator, I think, "OK, how come you immediately know it does this [assuming you don't just recognise the circuit from a textbook]? What prompted the original designer to try this particular circuit?" EEs I've met - unlike a lot of mathematicians, I think? - don't seem so keen on explaining their thought processes. This may sound weird, but I'd love to have one as a social friend, who would just lead me through building shit for fun.

  • Re:Handhelds (Score:4, Interesting)

    by Xest ( 935314 ) on Tuesday July 23, 2013 @10:44AM (#44360949)

    It's not just that, as companies have been cutting staff they've also been looking for ways to do more with less staff and turns out that that's where computer automation comes in. The reality is there are some jobs out there whereby you can hire one developer and have him/her write software that will automate the job of 10 people or whatever. It's cheaper to hire a developer and automate, than to keep paying people to do an easily automated job.

    That's why software has been fairly recession proof. There have been redundancies of course, but for each redundancy there's been plenty of other companies looking to hire to automate.

    The mobile boom has helped as well of course as you say.

  • by inasity_rules ( 1110095 ) on Tuesday July 23, 2013 @11:24AM (#44361279) Journal

    To understand circuits "intuitively", you need to train yourself to visualize both the voltage, currents and frequencies at any point in the circuit simultaneously. When you can look at a diagram of a filter and "see" the waveform or frequency comming out, then it is intuitive. It sort of comes with experience. And you start to recognise patterns which simplifies things. It is a lot like learning to read, or program a computer, just more complex in that something further "down" the circuit can have an effect on something further "up".

    The trick with most oscilators is to realise that noise starts them. In a perfect world, they'd need a kick to get going. Most things are tried because, like with any engineering, when all the components are understood, all it takes is a bit of intelligence to combine them into useful modules.

The rule on staying alive as a program manager is to give 'em a number or give 'em a date, but never give 'em both at once.

Working...