Jason Voorhees
Say cheese
- Joined
- May 15, 2020
- Posts
- 74,377
- Reputation
- 214,574
One thing I’ve realized after grinding in CS for a few years it’s nothing like mech or civilbwhere the learning curve flattens out post-grad. In CS, you’re never done leveling up and learning.
Tech sprints forward at warp speed new frameworks, languages, architectures, and paradigms drop every year. Your degree is nothing more than a fancy ticket for networking and opening doors, but it won’t hand you real world skills on a platter. Top schools like Harvard or Stanford still teach HCI or compiler design with legacy systems, and DevOps tooling is barely on the radar in most curricula. Academia can’t keep up with the meta shift, so you HAVE to self-teach via side projects, bootcamps, workshops, or hackathons.
Employment gaps are a more or less a death sentence in this field. recruiters smell stagnation from a mile away.Compare that to mech or civil master thermodynamics or structural design once, and those principles hold for decades In CS, fundamentals are just the start You gotta keep stacking skills non stop.
That’s the double edged sword it's fun when you’re in the flow, but draining if you’re not obsessed. I've seen grads from elite unis flop hard if they coasted on lectures without grinding personal projects or open-source. You need to *love computers and eat problem-solving for breakfast. If that’s not your vibe, you’ll burn out fast and regret it. I've seen many casuals come into CS and fail to get jobs and do well because they were in it only for the money. There is huge money to be made ofc. But that comes with large asterisk
Tech sprints forward at warp speed new frameworks, languages, architectures, and paradigms drop every year. Your degree is nothing more than a fancy ticket for networking and opening doors, but it won’t hand you real world skills on a platter. Top schools like Harvard or Stanford still teach HCI or compiler design with legacy systems, and DevOps tooling is barely on the radar in most curricula. Academia can’t keep up with the meta shift, so you HAVE to self-teach via side projects, bootcamps, workshops, or hackathons.
Employment gaps are a more or less a death sentence in this field. recruiters smell stagnation from a mile away.Compare that to mech or civil master thermodynamics or structural design once, and those principles hold for decades In CS, fundamentals are just the start You gotta keep stacking skills non stop.
That’s the double edged sword it's fun when you’re in the flow, but draining if you’re not obsessed. I've seen grads from elite unis flop hard if they coasted on lectures without grinding personal projects or open-source. You need to *love computers and eat problem-solving for breakfast. If that’s not your vibe, you’ll burn out fast and regret it. I've seen many casuals come into CS and fail to get jobs and do well because they were in it only for the money. There is huge money to be made ofc. But that comes with large asterisk
