Day 4: The Degree Dilemma
I'm a CS student in semester 4. I also run two companies. Honestly? I'm not sure the degree is worth it, for me.
Let me be precise about what I mean.
I'm not saying education is useless. I'm saying a CS degree, for someone already running production infrastructure and shipping real software, is a poor use of 4 years.
Here's my reality:
- When I study networking protocols in class, I already understand them, because I've debugged them at 2am when a router config broke and 200 customers lost internet.
- When I study databases, indexes aren't abstract, I've watched queries time out on a live FreeRADIUS database serving real users.
The classroom isn't teaching me anything the field hasn't already taught me better, faster, and with actual consequences.
So why am I still enrolled?
Well, social pressure, family expectations, and the nagging fear (not mine, the people close to me fear this) that the one time I need that piece of paper, I won't have it.
Not exactly a compelling academic mission.
I think the degrees, especially in CS, made sense when information was scarce and credentials were the only signal of competence. Neither of those is true anymore.
What signals competence now: things you've built, problems you've solved, systems that run in production with your name on them.
I have those. The degree is catching up.
Day 4 of my 30-day build-in-public series. Every day I share what I'm actually building, at ViberNet and at my software agency.
Say the thing. Own it.