It's mostly unsafe if you suck.
The programs are dumbed down quite a bit.
In the name of getting more students, Computer Science programs now tend to cover shit languages like ruby, maybe python if you're lucky. They teach you how to program, sure.
This is somewhat good in that a good programmer shouldn't only be proficient in a single language, but I often see programmers who aren't really proficient in ANY language as a result. Sure, they can do maintenance in a lot of them, but there is a definite ceiling in what they can accomplish that is lower than that of the peers older than them.
The compsci folks in my age range and older spent most of our college careers in C++, some Assembler, and Java. You typically STARTED in C++, and might take one course in a simpler language beforehand. We've all been able to learn new language in a month at other jobs in the past, and the time spent becoming really GREAT at those languages teaches us important lessons.
(Mostly, that you almost certainly don't know everything about the language you're writing in, heck if it's a big enough language (C and just about all of it's direct/indirect descendents qualify) you don't know shit about it. which is huge because it creates a level of arrogance where even giving someone a code sample to show how they fucked up isn't enough.)
But even worse, it almost feels like the people I see come in and out nowadays have spent so much time grasping the language for a given course that they do not have the same grasp of really important stuff. Sure, they all know what a linked list is. If I'm lucky, they can understand Big-O Notation. But implementing a fast sort or a hash? Actually debugging network communications problems? Understanding how to make shit that won't completely crap the bed in a real world usage even though it works fine under light load?
good luck with that.
The other problem aside from dumbing down of the programs (which makes you less valuable potentially) is the bit where people don't want to live where the work is, or don't want to do the work.
For the type of programming I do and where I live, I have recruiters emailing me almost daily with new opportunities that pay well when you consider cost of living. I only make what a junior to mid tier developer would get in California (I'm considered high tier), but an apartment is typically 1/3 to 1/4 the price of what I'd pay here.
There is a bigger problem in all of this, which is the push to use javascript hacks as developers thanks to node.js and similar technologies. It's an attempt to cut down the average salary of Developers, but it doesn't seem to be working the way people expected. They're realizing very quickly that they still wind up having to hire Java/C++/.NET folks to do anything they can't find a package for on NPM that is as easy to integrate as a geocities counter.
That's not to say there aren't good node devs out there. The problem is there's a huge gap between the few good node devs and all the JS hacks.
Again, the one plus side is it seems to have backfired in a number of places and demand for competent people is shooting back up.