If you’re in the position to do so: try getting a job as a software developer for a year before going to college. If you’re able to demonstrate you’ve already worked on your own projects, you will be taken more seriously than cs majors fresh out of college who’ve only seen code in home work assignments. Do this to get to see how software development works as a career and see if you fit in it.
You don’t generally need a degree to be a programmer and in this field, experience is often more valuable than a degree. What college can offer is connections and the opportunity to find your actual calling.

Depends on scholarship/FAFSA.

College still will give you connections. Maybe you will want to look into research positions in CS later after meeting a few professors too.

Also useful to have people your age in your field just around. Could get really into a subfield like robotics or IoT through it.

But if you don’t have any scholarship, and you live in US with a $8000/sem prices, then I don’t think it’s worth loans.

Hope this helps!

Well, the IT job market can change very quickly, so it is very difficult to predict what the job market will look like when you enter it in around 6 years (I assume that’s how long it will also take in the US to get a Bachelor + Master?). It could be that in 6 years the AI bubble has popped and dumb managers will realize that AI can’t replace every Software Developer.

I’d say go ahead and study CS, and if you can’t find a job as a Software Developer, you can then look in neighboring IT fields, such as System Administrator, where you (for example) have to administrate Linux servers, and since you say you already have experience with this, it should give you an advantage in applications.

Whatever you do, don’t be evil.

My take is that right now we’re in a software building boom. Making software is a lot cheaper now but maintaining software not as much. I think programmer numbers right now have flatlined but will probably grow in the future as we write more software.

Pivoting to trades is a much safer choice and healthcare will be a guaranteed job security because of demographic changes.

It’s honestly hard to say. It’s very impressive what AI coding can do, especially in the past year, but all AI companies are not making a profit. They’re effectively subsidized by investors. They’re focused on growth. At some point they’re gonna need to make a profit, they cannot continually operate at a loss and focus on growth. In fact, when Microsoft started charging properly it was such a massive deal that they called it the tokenpocalypse.

Honestly, I hate to say it, and I’m not trying to be a tech bro, but I think AI is here to say. What exactly it looks like long term, it’s hard to say. I can say this though, knowing how to program will make you a better vibe coded (I feel dirty saying that seriously). So even if AI becomes the norm, you’ll be better positioned if you know what you’re doing.

When things turn though, it’s impossible to say. It could be in the next year, could be like five years out. It could be that when you’re done with your four year degree, they’re still out here doing this “AI is gonna fix everything and we don’t need junior devs” song and dance.

TL;DR: AI is not profitable now so will get more expensive meaning they’ll have to use it less. Either way, knowing how to program without AI will make you better at programming with AI.

For the first time in over thirty years, the community college near me has had many members of the community advisory board (reps from various local businesses) that rep’d tech firms not even come to the advisory board meetings.

I take that to mean they’re riding the AI bubble, hoping to phase out much of their human workforce. That said, someone has to maintain the local infrastructure, and while data centers don’t employ many workers, they need some staff to watch over the systems. I also think networking still is a strong field, and obviously cyber security.

I have worked with several folks that were much better at their job because of self-hosting, so your experience there maybe isn’t as worthless as you think.

My advice would be to talk to recruiters and department heads and ask what they see themselves needing.

If you are interested in the internals of computers just as much as programming them, take a good hard look at Computer Engineering as a major instead. You still get to code, but you also get to understand the hardware underneath it all. Since it is rooted in the physical parts of computing, I think it is less likely for AI to eat those jobs. (Plus, everything from your car to your TV to your coffee maker has an embedded microprocessor in it now. I think embedded software is a safe bet.)

But, no matter what major you pick, it is no longer the case that simply graduating with a degree (and a good GPA) is a guarantee of a good job. You need to go beyond your classes, and find additional things to work on. Internships are great if you can get them, but even if you can’t, try to find an open source project (or even a hobby project) that you can spend time on. You want to have something more than your coursework on your resume for those first jobs. I would even value a resume with some good internships or side projects and a 3.6 GPA over someone with a 4.0 GPA who did nothing else (and left me with nothing else to talk about during the interview).

Finally, whatever you do, don’t extend yourself to go into debt. Maybe there are a small handful of CS schools that are worth going into debt to attend – but let’s face it, if they want you and you’re good enough, they will find a way to get you to afford it there, and you will get hired somewhere if you can make it to graduation. But, I know folks who went into 100+k worth of debt to go to a CS program at a small liberal arts college because they liked the campus. Don’t be that person. Unless you are MIT or Caltech material, your local State University is probably good enough. If you do get through 4 years of school and can’t find a job in your field and need to pivot, that will be so much easier to do if you have as little debt as possible.

Not nearly as bad as the now headline news presents.

Tech unemployment is still just about the lowest of any industry. Pay remains competitive (although nothing like the $200k entry level jobs of the 1990s). The labor demand is definitely growing, both domestically and globally.

Silicon Valley is shedding jobs. But if you go chase a job at EPIC up in Wisconsin or JP Morgan out in New York or take a job at Deloitte or SAP or Schlumberger, you’ll find them. Look for positions in the airline or finance or real estate or energy industries, there’s a superabundance of work and a perpetual shortage of labor.

Most of these big corporate outfits are glued to Microsoft products, though. Oracle also remains a popular database environment. Or they’re using some proprietary nonsense - Dell Boomi for visual programming of interfaces or UIPath for botting or some other ill-conceived overpriced insanity.

But - at least where I’m sitting - AI hasn’t replaced shit. My office is still trying to implement Agile and we’re a Fortune 100 company. Most firms are way behind the curve. Don’t let the hype cycle fool you.

If you actually care it’s a good time. It has never been as easy to learn and get into software engineering as it is today.

Thanks for all your help everyone!

The CS job market is very location specific, so I don’t have much advice in that regard.

I’ve got quite a bit of experience with Linux and I manage a home server, but that probably doesn’t differentiate me much.

That said, I have been on my company’s rotating interview panel for about a decade now, and while my company’s line of work involves a lot of Linux development, I can say that most of our college hires do not possess very much Linux background at all. Sure, they might have used Linux machines for school projects, but rarely do any of them assert to be “experienced” with Linux.

By that, I mean deeper knowledge than just using Bash. If a candidate can tell me why they prefer csh over Bash, or any syntax difference between POSIX sh compared to Bash, that is definitely a distinguishing quality. It speaks of an operator who has enough usage under their belt that they’re annoyed by the typical distro’s defaults, and more importantly, assessed the available tools, and picked the right tool that works for them.

I cannot understate how valuable it is to us to find a candidate that understands their tooling, especially right out of college. Considering that we assume most new hires have to be brought up to speed over the first few months, a candidate that saves us that effort is at least one rank above their peers.

Deeper functional knowledge comes in other forms as well. It’s one thing to know how a C program’s main() function is invoked by an OS, but anything which shows a fuller understanding of, say, system architecture and how a timer interrupt leads to a context switch in an assembly ISR, to a returned service call to load an ELF, to a CPU privilege ring change, to crt0, to main(), that is another level entirely.

I’ve interviewed candidates that had side projects involving retro game disassembly. So maybe they couldn’t give me the above level of detail for x86, they could describe the same for MIPS. And that’s good enough, because most architectures do roughly the same thing, with a few different semantics and names.

Circling back to managing a server, if you had to deal with PAM, NAT and port forwarding, tunnels and VPNs, compiling from source, or abything like that which is non-trivial, do not sell yourself short. All that stuff is resume material, because if you can relay to an interviewer that you’ve dealt with real network or machine security tasks, it is distinguishing.

The best part is that you have all of college to learn the CS curriculum, but it’s also time that you have to pursue any particular focus that excites you. I’ve written earlier about how embedded engineers don’t really get caught in the hype cycle, so jobs don’t suddenly appear then disappear a few years later. If you wanted to do that route, getting started with any microcontroller (eg Arduino, STM32) would help, with a goal to understand all the “magic” that the IDE and compiler are doing. Maybe instead you like das blinkenlights and find yourself drawn to hardware design. It wouldn’t be too late to consider a switch to the Computer Engineer (CE) major, so you have a small taste of the EE life.

CS as a field is so large that there are many routes between “I want to work with computers” to a declared major and to a career thereafter. Fortunately, time is on your side; this would be a very different conversation if you were a 4th year college student.

If you have any decent spatial skills, maybe look into GIS. I see positions for GIS developers constantly. More than I ever see positions for GIS Techs or Analysts.

Also if you’re in the US, check out BLS.gov, it can help you find similar career fields or specialties that maybe you didn’t know about.

Talking from a European perspective, worldwide view here.

We know AI programming is not viable on the professional field. Some companies are not up to date with that yet though.

So I hope when the AI bubble ends in one way or another you will be needed and wanted.

Speaking on a personal level, if you’re into computers and not just there for the money you’ve got an advantage because those only there for the money are often a bit lacking for the job.

Just saw your other answer. I think security and networking is always a hot topic and open. Currently working in exactly those fields. Ama if you wish.

As a high school senior self-hosting, you are at least a couple years ahead of the curve in your cohort in this area. Don’t write yourself off, even if you are just half-blindingly running scripts for now, keep exploring and tinkering, then learning will come naturally with it.

Assuming you are in the USA, unemployment is low yet few are hiring. Trump’s tariffs and meddling in everything has made many businesses across the world hesitant to make any hiring or firing decisions (aside from Silicon Valley tech which thinks AI will do all the jobs). I’ve encountered several reports like this over the last year, which means if you were a new grad looking for a job right now, in many fields you would struggle to find one.

Definitely ask recruiters for their insight on job market trends, and also start talking to employed people in the fields you have an interest in. Ask if their department recently hired or had layoffs, and other questions to help you decide if that’s the kind of work you could see yourself doing in the future given honing your skills through higher education and hobby development.

One kind of career that sounds up your alley based on the skills and interests you described could be systems administration. Those roles will still be necessary for the most part, AI or not.