# Should you study software engineering?

Alfonso Campodonico · 2026-11-06 · https://alfonsocampodonico.com/posts/should-you-study-software-engineering

> Agents write the code now. The degree was never really about the code.

## The question

Some version of this comes up every semester. If an agent can write the code, why spend five years learning to write it?

It's a fair question. I write less code by hand every month, and the code I don't write is often better than what I would have typed. So the short answer from me, someone who teaches it and works in it: yes, study it.

## What got cheap

Writing code got cheap. Not free, but cheap enough that "I know the syntax" stopped being worth much. A student with an agent can ship a CRUD app in an afternoon, and so can someone who never took a class.

If that's the job you want, a degree is a slow way to get it. Build things, ship them, and learn on the way. That path is real, and plenty of good engineers took it.

But that was never what the degree was for.

## What didn't

What I teach is operating systems and distributed systems. None of it is about typing. It's about why a process gets killed when memory runs out, why two servers disagree about who the leader is, why a lock that works on your laptop deadlocks in production. Agents are happy to write the code for all of that. They're less reliable at telling you code is wrong without proper metrics, and you can't understand if something is wrong at all if you don't know what wrong looks like.

That part is still expensive. The bugs that wake you up at 3 am rarely live in the code you just wrote. They live underneath it: a disk that filled up, a network that split in two, a pod the scheduler has nowhere to put. An agent is a good shovel. You still have to pick the spot, and you have to notice when it digs up nonsense.

Fundamentals age slowly. The scheduler in your kernel works on ideas older than you. [Consensus papers from the 80s](https://doi.org/10.1145/62546.62549) still describe the systems I run at work. Frameworks change, paradigms shift, solving problems stays.

## What a degree actually gives you

Three things, and none of them is a skill you can list on a CV.

*Interactive diagram on the page: What a degree gives you.*

You build taste by living with hard problems long enough to see how your decisions age. A degree is one structured way to do that. It isn't the only one, but it's a good one.

## When I'd say no

Not everyone should do it.

*Interactive diagram on the page: Reasons to skip it.*

## So, should you?

If you like knowing how things work under the hood, yes. Agents make that kind of person more useful, not less, because they take away the typing and leave the thinking.

If you only want to ship, you don't need the degree. You need a terminal and [something to be mad about](/posts/spite-driven-development).
