11–20 of 75 posts
Earlier quoted context omitted.
I don't think we're talking about people who have never programmed before; we're talking about maybe COBOL and Fortran experts, or people who write low-level C but can only find Python and Ruby jobs.
Are we really at the point where engineers can't find jobs because they only know C++ instead of Python and Ruby web stacks? This is a bit concerning, if so.
A demand for workers is not the same thing as no unemployment. Plenty of people out there with outdated skillsets.
But that's their point. When you have people with no jobs, that counts for the unemployment. But even I know how difficult it is to find people to hire for our company as I do HR for a technology firm. There is a high demand, just shortage of people to fill the positions.
Earlier quoted context omitted.
But that's their point. When you have people with no jobs, that counts for the unemployment. But even I know how difficult it is to find people to hire for our company as I do HR for a technology firm. There is a high demand, just shortage of people to fill the positions.
I see an increasing unwillingness of companies to train people who don't have EXACTLY the right skillset. This used be different in the 90s.
To become a software developer (especially the kind with a CS related degree), you need: -A highly analytical mindset -The ability to handle tough math -The ability to read dense material and process it quickly -The mindset to persevere, test, investigate, and find obscure problems in complex systems -The ability to see a project through to its finish -The ability to explain complex logic and design, verbally and in…
And a 25-hour-a-week job doesn't seem that overwhelming. I think I worked 20 hours a week with a 30 minute commute each way - unless you're having a truly difficult time with the core concepts, a 15 hour course load and a 25 hour work load isn't much harder than starting any new job.
Earlier quoted context omitted.
But that's their point. When you have people with no jobs, that counts for the unemployment. But even I know how difficult it is to find people to hire for our company as I do HR for a technology firm. There is a high demand, just shortage of people to fill the positions.
I see an increasing unwillingness of companies to train people who don't have EXACTLY the right skillset. This used be different in the 90s.
To become a software developer (especially the kind with a CS related degree), you need: -A highly analytical mindset -The ability to handle tough math -The ability to read dense material and process it quickly -The mindset to persevere, test, investigate, and find obscure problems in complex systems -The ability to see a project through to its finish -The ability to explain complex logic and design, verbally and in…
Generalized, it means software -- the technology and the economy -- runs at a higher tempo. In order to step into the stream, you have to first match the new tempo.
I suspect that the rest of the economy stays in a slump because they are out-of-phase tempo-wise with software technology ... or that the tools that drive up the tempo of innovation in software has not made it out to the mainstream yet. (And even if it did, it will leave people behind simply because there are people who will refuse to impedance match).
Earlier quoted context omitted.
I don't think we're talking about people who have never programmed before; we're talking about maybe COBOL and Fortran experts, or people who write low-level C but can only find Python and Ruby jobs.
Are we really at the point where engineers can't find jobs because they only know C++ instead of Python and Ruby web stacks? This is a bit concerning, if so.
I spent a lot of late nights helping him come up to speed because he's not a bad guy. Even though he probably should have been doing this himself, the fact of the matter is that he chose poorly and now knows a lot about something that is growing less and less valuable every day. You can say that he's not an "engineer" but that's really just the No True Scotsman fallacy talking. It's really hard to compete on the job market when hiring managers just cut out huge swathes of your knowledge a priori, and the fact that happens is what concerns me.
Earlier quoted context omitted.
I don't think we're talking about people who have never programmed before; we're talking about maybe COBOL and Fortran experts, or people who write low-level C but can only find Python and Ruby jobs.
Are we really at the point where engineers can't find jobs because they only know C++ instead of Python and Ruby web stacks? This is a bit concerning, if so.