Today I'd like to talk about something I've seen brewing for years: the collapse of the "learn to code" dream.
According to a recent article in Futurism, new computer science grads are now facing unemployment rates worse than journalism majors. And if that sentence didn't trigger your internal error message, it should. The major that was once billed as the golden ticket to job security and six-figure salaries is now producing grads who are selling blood plasma to make ends meet.
But let's rewind a bit.
When I was in school back in the 70s and 80s, computers were still very niche. Nerd territory. We had a computer club that met after school, and it wasn't until my junior or senior year that they even added a proper computer class to the curriculum. You know, for credit. Before that, computing was more of a curiosity - a novelty - and definitely not something that was treated as a core skill. It was optional. Like typewriting. Or macrame. Or dodgeball (all 5 D's).
Back then, schools pushed this one-size-fits-all message: everyone needs to go to college. That was the goal they drilled into us, whether it made sense for the student or not. They didn't do nearly enough to promote trade schools or vocational paths. We need plumbers. We need electricians. HVAC techs, welders, mechanics. These are essential, high-paying, in-demand careers - but they got treated like backup plans instead of legitimate goals. The system tried to funnel every student into academia when a lot of them would've thrived working with their hands, building real-world skills instead of racking up debt for a degree they'd never use.
Then came the rise of Microsoft, the explosion of the Internet, and the digital revolution. Suddenly, everyone wanted to be a programmer. A lot of kids thought learning to code was their ticket to a dream job writing video games. It felt exciting - like the tech world's version of becoming a rockstar. And with esports blowing up, million-dollar tournaments, and streamers living in mansions, it wasn't hard to see why that fantasy took hold. Schools leaned into it, parents encouraged it, and the industry hype machine did the rest. Computer skills went from "nice to have" to mandatory. Curriculum changed. Districts went all-in. And the same educational system that once told every kid they had to go to college whether it fit their strengths or not... started telling every kid they needed to learn to code.
That was the message: Learn to code. That's your future.
And just like they did with college degrees, we mass-produced computer science majors like Pet Rocks. No concern for market demand, no guidance on fit or aptitude - just volume. Fast forward to today, and the market is flooded. Entry-level jobs have vanished. Unpaid internships are still a thing. Companies are offshoring, downsizing, or automating the exact jobs these kids trained for.
The result? Thousands of recent grads with good intentions, student loan debt, still living with mom and dad, and zero clue what to do next.
Now, let me be clear: coding is still a valuable skill. No, AI isn't going to replace every programming job tomorrow. In fact, I'd argue we're decades away from that level of disruption. But the myth that all you need to succeed is a CS degree and a decent GPA? That myth is crashing harder than a Windows Vista box with a bad driver install.
So what's the solution? Honestly, if you're learning tools like Microsoft Access or programming in general, your best bet probably isn't getting hired by some massive company that ghosted you after your third Zoom interview. It's hanging out your own shingle. Become a consultant. Find a niche. Help small businesses that still need real solutions. Most of them don't care about your academic history or whether you can reverse a linked list in under 10 seconds. They care about results.
Skills matter, yes. But so do timing, opportunity, and whether the industry is actually willing to make room for new talent. Until that changes, we're going to keep watching young developers crash into the firewall of reality - and wonder why the reboot command doesn't work. Learn to code if it fits you. Build digital skills because they're powerful. But don't fall for the hype that the degree (or even certifications) guarantees the job. It doesn't. Not anymore. And don't wait for the market to hand you an opportunity. Make one.
If you've got the skills and the drive, don't beg for a cubicle. Build your own damn starship.
LLAP RR
P.S. If you're a CS grad reading this and wondering if you should give up: don't. Just stop assuming the degree is the job. You're gonna need strategy, not just syntax.
P.P.S. It wouldn't be a Captain's Log if it didn't include a Trek analogy. I've got the perfect one: Just look at Wesley Crusher. He studied, showed potential, passed every test - but Starfleet still said no. Twice. It wasn't about skill. It was about the system. And he only truly thrived once he stopped playing by its rules.
I still contend that most anyone that graduates, isn't ready for the real world until they have at least three years' experience. More for accountants, lawyers and doctors.
I know many that hung out their shingle prematurely, including myself. That's a way to get into serious trouble or way in over your head. Possibly dealing with serious legal consequences that will dwarf that student loan. Even with forty years' experience in data processing and having written a RAD back in the 80s, it's still taken me two years of serious full-time writing/studying to get sufficiently comfortable in Access to say I'm now competent in my coding for the basics (exclude APIs, class modules, machine interfaces, etc.)
In university I first degreed in computer science and business. Even though I graduated in the golden age of demand, and in the top 5% of my class, it still took a recommendation from an industry respected professor to land that first good job. Actually, that job wasn't all that good, but it gave me time to learn real-world analysis and programming. I wasn't ready to hang out a shingle until four years after that job ended. But then again, there weren't online classes that could have flattened the learning curve.
Thomas Gonder
@Reply 12 days ago
To continue, having been the hiring manager/owner of a smaller sized business (less than 500 employees), I believe my dad's ancient recommendation for landing that first or any job where you're the applicant (not the pursued) is to say something like this to the owner or manager (that isn't some HR shield doing their best to weed you out).
"Look, I like the sound of this job. My career objectives align with the company's direction. Despite my education, I know I lack some qualifications you seek, but I'm a quick study. Based upon my industry analysis, I think a fair base pay is around $50k for what you're desiring as far as experience goes. I'll tell you what, I'll work the first 60 days at half that amount. If you aren't satisfied with my performance, I'll resign. Simple as that. In fact, here is my resignation letter postdated 60 days. Will you please give me the chance to prove I can do this job?
If nothing else, you'll stand out as bold and confident in a sea of applicants.
Michael Olgren
@Reply 9 days ago
If I might tack on... Just like practice, experience is good, but *attentive/focused* experience is better. @Thomas' comment about doctors not ready out of the gate is dead on. Worse, look at what the public's demand for cheap health care hath wrought-- PAs and NPs with two years' training can bypass the minimal seven that physicians have. I have to stop myself there. To quote Captain America, "I could do this all day."
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.