I doesn't seem so. It looks like there's a huge oversupply of software engineering and that will only make the salaries go lower.
I think something like a medical doctor or a dentist is a much safer bet. They have basically always been able to maintain high salaries for their work.
If you chose a CS degree for the easy money and don't actually enjoy programming, then no, I would say it's no longer a good choice. Yes, there were plentiful well paying, easy to get jobs cranking out code over the past twenty years but no boom lasts forever. Between both AI and a huge oversupply of coders, it will be very hard to get started in the next couple of years as a developer without above average determination and talent.
Is CS your passion? Stick with it. The job market isn't as good as it used to be, but it isn't as bad as people make it out to be. I am also pursuing a CS degree and I asked the same question here 6 months ago. Since then, this is what I've learned:
* Its likely that the slowing of the tech job market wasn't caused by AI, but by a change in the tax code (Section 174) and higher interest rates (companies over-hired during the pandemic when funding was abundant).
* LLMs may or may not increase developer productivity [1], and they definitely cannot replace software engineers entirely (and I don't think they ever will - but it depends who you ask)
* Anecdotally, finding a summer internship wasn't easy for me, but it also wasn't any harder than it was for my peers in other programs (engineering, finance, etc.). Job hunting is a skill that I think many people in CS don't have because it used to be easy.
* I used an agentic IDE extensively to code for my on-campus research job. I still enjoyed the job a lot, and even as an rookie developer, I still felt I played a very valuable role in my job that LLMs could not replace.
Yes, it’s still a good choice. The field has changed though. A few years ago, it felt like just having basic programming skills and a CS degree was enough to get started. Today, companies expect developers to understand software more deeply — problem-solving, system design, performance, and real engineering thinking.
I studied economics and philosophy at a medium sized state school, yet i ended up with the software engineers because of my passion for coding. Degrees are largely just checkboxes unless you're going to MIT, Stanford, etc.
With that being said, I did use my economics degree to get my foot in the door doing data analytics then I transitioned to SWE. You'll find you way, if being a SWE is truly your passion.
The business world is cyclic, and with that "programmer jobs" are also cyclic with the business cycle. So even though things look 'down' now, that does not mean that the down cycle will last forever. However, surviving through a down period as a new graduate will also not be easy in any regards.
As to AI, the current crop of AI (which is bubbling very well, and I believe is running itself quickly towards yet another AI winter [https://en.wikipedia.org/wiki/Ai_winter]), it may be useful for replacing some percentage of "head count" programmers, it is not likely to be replacing the actual creative, good, programmers (i.e., the one's often referred to as 10x). So the best advice I can give is to strive to really learn your craft such that you can function more towards the 10x side of the spectrum than the "head count" side. That will give you the best assurance of success at present.
My knee-jerk reaction is "No" if your goal is an easy-mode career that will give you a high salary right out of college, I think that dream is (largely) dead. If you really do love CS/related fields, I think there is plenty of room for you still, but it's no longer a free ride.
I graduated with a CS degree in 2012 so I fully benefited from the tech boom. If I were a senior in high school in 2025 knowing what I know now, I would probably go into Civil Engineering.
if you never programmed before college and you chose CS because it was a good job then you should change.
If you got into programming when you were a kid, can’t stay away from programming because you love it, and pursuing CS was an expression of this, then you should stick with it.
It used to be that there were only the second type because being a nerd wasn’t cool or lucrative. So this is just a return to baseline.
I absolutely hate the romanticism of the “good old days” when people only became programmers because of “passion”. I’ve worked professionally since 1996 and even then most people didn’t work because of “passion” they did it for money.
The people writing COBOL and FORTRAN on mainframes - I got my start writing C and FORTRAN on DEC VAX and Stratus VOS mainframes - didn’t speak about the joys of programming. They clocked in, clocked out and went on about their lives.
I doubt in 30 years across now 10 jobs I’ve met more than a handful of people that don’t have outside interests that they talk about at lunch outside of computers.
Whether he “loves” it or not is immaterial in the decision process. Whether someone will pay him so he can support his addiction to food and shelter is.
How many of the 2.7 million+ developers in the US wake up excited that they are creating Yet Another CRUD enterprise app ir some bespoke internal app that will never see the light of day outside of their company and thats the life of most developers world wide.
"The people writing COBOL and FORTRAN on mainframes - I got my start writing C and FORTRAN on DEC VAX and Stratus VOS mainframes - didn’t speak about the joys of programming. They clocked in, clocked out and went on about their lives."
FORTRAN was my first language in the 60s and I ENJOYED using it until "better" languages came along.
I debugged COBOL and once taught SQL to COBOL programmers while refusing to write anything in it.
I had my best fun with mainframe Assembler and CMS Pipelines.
I’m 100% sure that your passion didn’t come from growing up with computers in your home and hanging out with other computer nerds like the parent poster said. You also didn’t go home after work doing side projects on your home computer or contributing to open source.
By definition, before the late 70s, you had to leave your job at work and didn’t code on your free time unless you went into the office.
There were times I took a dial up terminal home. Before that in university, we had to punch our own card decks.
I didn't need to be at the office to write programs. All I need is a pad of paper (with maybe a few manuals) and a nice place where I can concentrate without interruptions.
It's become a lottery similar to pursuing a professional sports career. Similar to professional sports, the career duration is short. There's always kids coming up trained in the technology du jour who will work long hours for peanuts that employers will happily hire while they dump the expensive old guys.
You can do extraordinarily well as a founder if you find an opportunity, get it to market and build a moat that competitors can't surmount.
So it is definitely something a lot of people are going into and a person who doesn't want to face a bubble pop might consider something else. One good thing at Cornell is that we have a data science minor that anybody can take. I went to a talk by an English professor for instance who applies quantitative methods and data visualization to literary criticism.
I've seen others argue for schizotypy using the same biographical examples rotfl.
My working slogan now is "Schizotypes transmute coffee to coin (value)."
The flip side: (functioning) Schizotypes (adjoining academia) have lost their obsession with magic, AND self-diagnosed this loss with depression/anxiety/senescence etc. it's more subtle imho, but CS is a confounding factor* (muddling the pipeline between "dopamine" and "coin")
As to the below.. it's why I try to keep my credibility inscrutable on this site :)
*Used to be Math if you follow the Erdos quip and understand theorems as a long-now stand-in for "Coin"
"Good choice" for what? If you're not naturally curious about math, engineering, software and/or hardware, then probably not, otherwise maybe. Tech carpetbaggers out for a steady paycheck detracted from the industry more than AI ever has or will.. these people don't like mastery, learning, or excellence. Self taught but I had my doubts after transferring from CS to EE/CS, but I also took the 10 year route to minimize debt and maximize business work.
Ideally, I'd first try out or explore the intended field of work one wants to be a part of before fully committing time, money, and energy on credentials for it. This might take the form of one or more internships, reverse interviews of people in that field, and/or finding interviews about a particular person in that role or company. For anyone already enrolled, I'd still check out internships and such but only change majors if multiple internships were decidedly terrible.
Follow fun for you that others find tedious or uninteresting where there is great value requiring human-in-the-loop expertise or effort, e.g., find a defensible niche not exposed to 100% automation. That might be a STEM or financial specialty or sub-specialty that you find more interesting like biomedical informatics, data science, statistics, accounting, or actuary because becoming a generic software engineer is as risky now as becoming a generic systems administrator.
Ultimately, it's a personal decision that cannot be offloaded to others requiring some experimental research/trial and error in the real world™. Plus, it needs some luck and finding a mostly positive working environment which tend to be in short supply.
I doesn't seem so. It looks like there's a huge oversupply of software engineering and that will only make the salaries go lower.
I think something like a medical doctor or a dentist is a much safer bet. They have basically always been able to maintain high salaries for their work.
If you chose a CS degree for the easy money and don't actually enjoy programming, then no, I would say it's no longer a good choice. Yes, there were plentiful well paying, easy to get jobs cranking out code over the past twenty years but no boom lasts forever. Between both AI and a huge oversupply of coders, it will be very hard to get started in the next couple of years as a developer without above average determination and talent.
Is CS your passion? Stick with it. The job market isn't as good as it used to be, but it isn't as bad as people make it out to be. I am also pursuing a CS degree and I asked the same question here 6 months ago. Since then, this is what I've learned:
* Its likely that the slowing of the tech job market wasn't caused by AI, but by a change in the tax code (Section 174) and higher interest rates (companies over-hired during the pandemic when funding was abundant).
* LLMs may or may not increase developer productivity [1], and they definitely cannot replace software engineers entirely (and I don't think they ever will - but it depends who you ask)
* Anecdotally, finding a summer internship wasn't easy for me, but it also wasn't any harder than it was for my peers in other programs (engineering, finance, etc.). Job hunting is a skill that I think many people in CS don't have because it used to be easy.
* I used an agentic IDE extensively to code for my on-campus research job. I still enjoyed the job a lot, and even as an rookie developer, I still felt I played a very valuable role in my job that LLMs could not replace.
[1] https://metr.org/blog/2025-07-10-early-2025-ai-experienced-o...
Yes, it’s still a good choice. The field has changed though. A few years ago, it felt like just having basic programming skills and a CS degree was enough to get started. Today, companies expect developers to understand software more deeply — problem-solving, system design, performance, and real engineering thinking.
I studied economics and philosophy at a medium sized state school, yet i ended up with the software engineers because of my passion for coding. Degrees are largely just checkboxes unless you're going to MIT, Stanford, etc.
With that being said, I did use my economics degree to get my foot in the door doing data analytics then I transitioned to SWE. You'll find you way, if being a SWE is truly your passion.
The business world is cyclic, and with that "programmer jobs" are also cyclic with the business cycle. So even though things look 'down' now, that does not mean that the down cycle will last forever. However, surviving through a down period as a new graduate will also not be easy in any regards.
As to AI, the current crop of AI (which is bubbling very well, and I believe is running itself quickly towards yet another AI winter [https://en.wikipedia.org/wiki/Ai_winter]), it may be useful for replacing some percentage of "head count" programmers, it is not likely to be replacing the actual creative, good, programmers (i.e., the one's often referred to as 10x). So the best advice I can give is to strive to really learn your craft such that you can function more towards the 10x side of the spectrum than the "head count" side. That will give you the best assurance of success at present.
My knee-jerk reaction is "No" if your goal is an easy-mode career that will give you a high salary right out of college, I think that dream is (largely) dead. If you really do love CS/related fields, I think there is plenty of room for you still, but it's no longer a free ride.
I graduated with a CS degree in 2012 so I fully benefited from the tech boom. If I were a senior in high school in 2025 knowing what I know now, I would probably go into Civil Engineering.
if you never programmed before college and you chose CS because it was a good job then you should change.
If you got into programming when you were a kid, can’t stay away from programming because you love it, and pursuing CS was an expression of this, then you should stick with it.
It used to be that there were only the second type because being a nerd wasn’t cool or lucrative. So this is just a return to baseline.
I absolutely hate the romanticism of the “good old days” when people only became programmers because of “passion”. I’ve worked professionally since 1996 and even then most people didn’t work because of “passion” they did it for money.
The people writing COBOL and FORTRAN on mainframes - I got my start writing C and FORTRAN on DEC VAX and Stratus VOS mainframes - didn’t speak about the joys of programming. They clocked in, clocked out and went on about their lives.
I doubt in 30 years across now 10 jobs I’ve met more than a handful of people that don’t have outside interests that they talk about at lunch outside of computers.
Whether he “loves” it or not is immaterial in the decision process. Whether someone will pay him so he can support his addiction to food and shelter is.
How many of the 2.7 million+ developers in the US wake up excited that they are creating Yet Another CRUD enterprise app ir some bespoke internal app that will never see the light of day outside of their company and thats the life of most developers world wide.
"The people writing COBOL and FORTRAN on mainframes - I got my start writing C and FORTRAN on DEC VAX and Stratus VOS mainframes - didn’t speak about the joys of programming. They clocked in, clocked out and went on about their lives."
FORTRAN was my first language in the 60s and I ENJOYED using it until "better" languages came along.
I debugged COBOL and once taught SQL to COBOL programmers while refusing to write anything in it.
I had my best fun with mainframe Assembler and CMS Pipelines.
I’m 100% sure that your passion didn’t come from growing up with computers in your home and hanging out with other computer nerds like the parent poster said. You also didn’t go home after work doing side projects on your home computer or contributing to open source.
By definition, before the late 70s, you had to leave your job at work and didn’t code on your free time unless you went into the office.
There were times I took a dial up terminal home. Before that in university, we had to punch our own card decks.
I didn't need to be at the office to write programs. All I need is a pad of paper (with maybe a few manuals) and a nice place where I can concentrate without interruptions.
Quit school, join the trades. You can make as much money as you are willing to work for without the debt and it’s a pathway to being your own boss.
If I were looking at the landscape entering the market today instead of 30 years ago when I entered it, I would look into health care.
It's become a lottery similar to pursuing a professional sports career. Similar to professional sports, the career duration is short. There's always kids coming up trained in the technology du jour who will work long hours for peanuts that employers will happily hire while they dump the expensive old guys.
You can do extraordinarily well as a founder if you find an opportunity, get it to market and build a moat that competitors can't surmount.
No. Health related fields or something like that would be more sensible.
Well CS is basically majoring in AI… so I would say yea.
I am looking out my window at a new Computing and Information Science building
https://mastodon.social/@UP8/115500560220694978
and they merged the Computer Science, Information Science and Data Science programs into one big department that enrolls 2000+ students
https://milestones.cis.cornell.edu/
So it is definitely something a lot of people are going into and a person who doesn't want to face a bubble pop might consider something else. One good thing at Cornell is that we have a data science minor that anybody can take. I went to a talk by an English professor for instance who applies quantitative methods and data visualization to literary criticism.
Other academics think it's bipolar (the 6-7 version of FOMO really) that provides value
https://www.its.caltech.edu/~matilde/DarkBrightness.pdf
I've seen others argue for schizotypy using the same biographical examples rotfl.
My working slogan now is "Schizotypes transmute coffee to coin (value)."
The flip side: (functioning) Schizotypes (adjoining academia) have lost their obsession with magic, AND self-diagnosed this loss with depression/anxiety/senescence etc. it's more subtle imho, but CS is a confounding factor* (muddling the pipeline between "dopamine" and "coin")
As to the below.. it's why I try to keep my credibility inscrutable on this site :)
*Used to be Math if you follow the Erdos quip and understand theorems as a long-now stand-in for "Coin"
It's a good choice if it is what you want to do.
A bad choice if it is something you don't want to do.
And a reasonable choice if neither of those apply.
Good luck.
"Good choice" for what? If you're not naturally curious about math, engineering, software and/or hardware, then probably not, otherwise maybe. Tech carpetbaggers out for a steady paycheck detracted from the industry more than AI ever has or will.. these people don't like mastery, learning, or excellence. Self taught but I had my doubts after transferring from CS to EE/CS, but I also took the 10 year route to minimize debt and maximize business work.
Ideally, I'd first try out or explore the intended field of work one wants to be a part of before fully committing time, money, and energy on credentials for it. This might take the form of one or more internships, reverse interviews of people in that field, and/or finding interviews about a particular person in that role or company. For anyone already enrolled, I'd still check out internships and such but only change majors if multiple internships were decidedly terrible.
Follow fun for you that others find tedious or uninteresting where there is great value requiring human-in-the-loop expertise or effort, e.g., find a defensible niche not exposed to 100% automation. That might be a STEM or financial specialty or sub-specialty that you find more interesting like biomedical informatics, data science, statistics, accounting, or actuary because becoming a generic software engineer is as risky now as becoming a generic systems administrator.
Ultimately, it's a personal decision that cannot be offloaded to others requiring some experimental research/trial and error in the real world™. Plus, it needs some luck and finding a mostly positive working environment which tend to be in short supply.
Good luck.