Imagine that! And here I had thought this new "common core" would leave our snowflakes even less prepared for the exciting world of retail sales and customer service than before... But, I clearly stand corrected!
Security through obscurity!
Another aspect of the problem - Corporate policy in most large companies is to treat all of your IT programmers as identical widgets. This policy stems from HR, Finance, and IT efforts to 'normalize' positions so they can be circumscribed enough to allow 'efficient' allocation of resources, or more damaging, the allocation of resources that can be outsourced wholesale. Ultimately it all comes down to cost reduction. Poor results of IT, coupled with IT being strictly a cost center - leads to this outcome (the cost vs. value proposition as seen through the eyes of the heads of the business).
This of course, drags down everyone with it causing many good people to leave or get caught in the outsourcing net. If they are lucky - they do manage to move up into management (architects etc) - and hopefully they can influence the designs - but again - what is left behind is tragically impossible of effiently implementing even the best designs - so the problem feeds itself as your best get pulled away from programming.
Indications are CTOs are starting to see how this is not working...here's hoping they can get the HR and Finance people to turn this around, but I doubt it. .
No, there are a lot of STEM graduates who really aren't that good and don't have much experience, yet they believe they're entitled to a senior-level salary. I am more than happy to pay a high salary to a candidate who is actually good at their job and has a demonstrated track record of performance. The glut of average performers with little more than student projects as experience, however, are not worth more just because I have open positions to fill. The key is will this person actually perform at the position I put them in rather than just fill a desk and surf the net half the day.
Too bad you posted anonymously. I would have modded you up. This is absolutely the truth.
My recommendation for anyone: if you love the carreer you want to get into - then do it. However, if you only see a bunch of dollar signs - then it is better off for you and the rest of us in STEM if you would put your energy into something else.
We are plaugued with a glut of people who cause more inefficiency than the 'solutions' they create... causing me, and others who know what they are doing to spend extra cycles fixing their broken systems. The problem is most of the time, they don't even know why their choices are a bad thing, or worse - if they do, they don't care allowing expediency to take precedence over quality.
On a positive note: this will keep me employed well beyond my retirement as a contractor fixing other people's code.
For the victim, death of the criminal brings an element of closure. There is -zero- chance of them coming back to haunt the victim; both in jail and out of jail. And that's really what the death penalty serves; both justice and closure for the victim/s involved.
ASCII a stupid question, you get an EBCDIC answer.