Who's saying don't get a CS degree???? The field has changed a LOT recently. Sure you don't *need* the degree, but is it going to get an HR manager (who doesn't necessarily know too much about what you need to do SD) to not immediately toss your application in the recycle bin? Yes. I haven't seen many software dev jobs lately that *don't* ask for at least a bachelor's in "related field," or years of specific experience.
Nobody is saying that, but it would be easy to make the argument that a CS degree is worthless, especially at high private school prices, because a CS degree isn't a guarantee of a job and if an applicant is young it's a pretty good indicator that they don't have any real-world experience.
And "web dev" or "sysadmin" aren't a protected terms like "lawyer" or "registered dietician" and don't require a dedicated license like some kinds of engineers so there's no need to bother with a BS, it's just a frivolous waste of time encouraged by ivory-tower professors who are going to make you jump through hoops with contrived exercises and learn programming languages nobody has used in thirty years.
People who go to school to get CS degrees are just wasting their time on their hobby, and how many of them actually end up working as web developers or tech pros anyway? If they didn't want all the debt that comes with a CS degree they should have gone through a diesel mechanic program or just started their own business instead of wasting four years on hangovers while some IBM burnout droned on to them about COBOL. They could have just taken some A+ courses, tested for a few Microsoft Certs, and done a few coding bootcamps if they really wanted to work in tech; spending $200k on a degree just shows they don't have good judgement and you shouldn't hire them.
(please imagine a sarcastic tone and lots of air quotes in the last two paragraphs)
All of which is to say that *no* degree is a guarantee of work, or a guarantee of education, or a guarantee of skills, but you constantly hear "humanities are a waste of money, get a degree in STEM."
The best sysadmin I know has a technical theater degree. The richest person I personally know has a degree in linguistics and owns a record company. The guy who runs the bullet company my spouse used to work for has a PhD in Education. The best English lit professor I had had a Bachelor's in biology. My boss dropped out of college to start the business he is still running 40 years later and he had to hire me because he can't write emails. My dad went to one of the most expensive schools in the country on a full scholarship and got a Master's in Rhetoric and his brother became a city mechanic and they are both happily retired after 35 years of stable state employment. My sister went to the same school as my dad and got a similar degree with a shitload of loans and is a temp worker. My spouse went through a community college machining program and decided that would serve him better than a mechanical engineering degree. I have friends who both graduated from the same school I did, one of whom is a roboticist working with JPL and one of whom is a civil engineer working with sewers, and the roboticist is the one whose job is *much* more precarious. I have a friend who has a CS degree who couldn't hold a job in the field and just got certified as a private detective. He's married to my friend who has an Associate's degree in English and who does InfoSec for a large NGO. My former operations manager had an MBA and is the CIO of a biomedical firm. My current operations manager has no degree and used to work at a phone kiosk in the mall.
I think that one of my biggest problems with the narrative of "humanities degrees are a waste of money, you should major in STEM" is that what it does is sell a lot of very expensive STEM degrees to people who are still going enter a job market full of people trying to pay off their very expensive STEM degrees.
Takeaways:
No degree guarantees you a job in anything. There are a few universities whose prestige and connections/ability to reach out to pretty high-level people might help guarantee you jobs, but it's got nothing to do with your degree. It's about the connections, and to an extent how confidently you can blag your way through an interview and make your contributions to your existing side projects seem more important. (If you have connections, "coding/technical interview? Don't know her")
If you're going into research - YES. Going to uni and working on projects and doing research under CS profs still helps. Build the relations, make sure that they can write you personalised recommendation letters! Can you go on to research at companies? Yes, but again, the degree does help in those cases too. My team leader at my internship revealed that the company had a target number of research papers to publish each year, and that affects things like which conferences they aim to present at (e.g. we can make waves at country-wide/Europe-wide conferences, or North America-wide conferences, or even at associations of engineering companies, but not the IEEE. This is just a hypothetical example btw). It can affect the quality of research you get to do, so take that as you will. If that's not for you and you want to do academic research? You still need uni.
Unis are ONLY about a start. Once you get your first major computing job, it's all about the work you've done, the technical knowledge you've acquired (boy how companies would love a hire with insider knowledge...) and any ways you've demonstrated that you're a good learner. That you have learned HOW to learn. Computer science is a fast-moving industry, everything breaks, everyone needs technology or wants to integrate it into their work nowadays anyway, and save for software-for-the-sake-of-software companies, most computer science positions are within a company where you need secondary specialised knowledge. Be it in communications, hardware, medical knowledge, financial systems, psychology/graphics, telecom, whatever. You are often building solutions for specialised industries and need to show that you can learn about them enough to understand what you're building for. Demonstrate through projects, an older job, something outside of college. And after the first couple of software jobs you've been through, your degree is just the name of your university on a paper.
Unfortunately the anon is right about one thing: especially early in your career, they are looking for something computer-related on your resume. It's not specifically a CS degree. It could be courses, projects, clubs, work-study positions, internships, it doesn't matter. They're not looking for the words "B.Sc, Computer Science" though. I've seen people in computer science minors get far better positions than those in the major programs. They have more diverse knowledge that lets them work interdisciplinarily—that's a huge plus in this field! (Why? See the previous point)
That said, it's not impossible to start at a company and then try and move into computer science-related positions within it.
Last, if you are going to go into a computer science degree, please please make the best use of it! It's not just about learning how to code, it's not just about memorising some algorithms and database concepts, it's not just about learning C++, Java and Python and making a little app with some code behind it and putting it on your github and some of you all make me sick, I hate you. Learn about computer science. Learn about what it does, how it interacts with other fields. Expand your horizons a bit, it's not just about websites and apps. It's not just about AI and ML or blockchains. Learn to think about computer science differently. Don't limit how you understand the word "technology". A toaster is technology, and very efficient technology indeed! (Very user friendly, for example. It simply won't press down if it's not plugged in) A rolling ball inside a box, amazingly, is a core development of computer technology—the mouse! It's practically an application of psychology (the principle of "grouped objects move together"). One of the few advantages of going to (most) universities is that you get to take electives. Use them well!
If you've ever wondered why scholars in the past used to be known as "mathematician, astronomer, linguist and polyglot, musician, painter and philosopher", it's not because they had 48 hours a day. It's because all these fields are related. We forget that. We like to box our degrees into "computer scientist" and "engineer" and "humanities student", but really what they all are, are applied maths and observation. (I could go on about this for a looong time, but I won't here)
Use your electives well! Bring in other perspectives into your knowledge of computer science! This can of course come from life experience, but being at university is one way to get that kind of exposure at 3x the speed that life might present it to a 19 year-old. Of course, again, your primary major doesn't even have to be computer science. It's really just about demonstrating that you know how to think about things, and how to learn.
(Moral of the story: no subject is a waste of time, and knowing one, and nothing of any others, is a one-way ticket to some of the disaster tech we're seeing today)
To reiterate: especially in computer science, being a jack of all trades is a very good thing actually!