Why a CS degree and algorithmic problem-solving matter more than ever
A formal degree and algorithmic problem-solving is the answer. Always has been
A developer argues that formal education and algorithmic thinking are essential for a successful software career, especially in a post-AI world. Drawing on anecdotes of colleagues who lacked these foundations and caused chaos, the author contends that a degree and 'leetcode' practice provide a crucial edge, despite acknowledging the financial and systemic barriers to obtaining them.
Stay in school, don’t be a tool, learn to problem-solve for the love of the game.
- Dove
Excellence is what matters. It can be found in universities (and is in theory what universities are for), but in my professional experience, a C.S. degree is no guarantee that one has been trained with excellent taste and judgement. In fact, I usually react to the new hires with C.S. degrees with some degree of frustration at what schools are teaching these days.
Excellence can also be found in independent reading, and it can be learned with professional mentors as well.
You can learn it from AI, too, actually. I'm skeptical about the central use of AI in writing code directly, but find it incredible as a teaching tool. It is especially impressive when I use it as something between a tutor and a search engine, talking to it a lot about the best way to do things and asking it about standard methods and resources. It's not infallible, to be sure, but it's this incredible combination of tutor and textbook, with a better connection to the zeitgeist than all but the very best of tutors and textbooks.
In this way, AI is not dissimilar from school, independent reading, or work experience: you can use these tools in different ways, to serve different goals. If you focus on credential, skill, productivity, and money, you may entirely miss out on excellence in your craft. On the other hand, you can pursue excellence in any of these contexts.
- hellisothers
Classic gatekeeping argument insisting a CS degree is necessary to write good software. I don’t have one and have 20+ year successful career with accolades, know many others in the same boat. Obviously there are CS degree people who were also successful, and the flip side comes for both camps, I’ve worked with absolutely awful engineers with or without a CS degree.
It is a signal, not the signal.
- codemog
Guy writes like he’s the main character when he’s probably dev #48373 at CrudCorp. I bet the internal company tool he works on is pretty slick though.
Most smart people I know don’t like toy leetcode problems, they like real problems which are orders of magnitude harder and not solvable by LLMs. Leetcode is for people who got good grades and want to feel smart by learning the rote tricks to solve leetcode.
- spudlyo
I'm not sure how this kind of software gatekeeping squares with our new glorious future where everyone is happily running bespoke vibecoded applications tailored specifically to their needs.
I bristled a bit at the scalpel "you don't want to give this tool to the wrong person" analogy. While I agree that there are certain classes of software (like banking/finance, healthcare, etc) that you don't want just anyone writing, but you don't need to have a C.S. degree to whip up a SwiftUI Music.app replacement so you can listen to dad Rock while you work in the basement.
- jnwatson
I have a CS degree. I learned some useful things. However, I graduated in 1998. I've had to learn a bunch of stuff since then because it didn't exist in 1998.
For folks that don't have CS degrees, they just have a little more to learn outside college. When I started my career, a significant majority of my colleagues didn't have CS degrees. It just wasn't a popular major in the 90s.
Among the best developers I've ever worked with never went to college at all.