upvote
That's something I found more and more as I get into my career

Stuff like programming languages, frameworks, tools all come and go throughout your career

Whereas the core concepts/theory you learn in a CS degree don't change from job to job

When I was in undergrad I wished we did more practical hands on work, but now later in my career I'm glad we didn't because its easy to self learn that stuff and it goes out of date anyway

reply
Skip the easy stuff and spend your energy on the hard stuff is excellent advice for anyone doing a cs degree. The easy stuff you can google. The hard stuff is what will mold your mind into a sharp tool and you will never get the same chance to spend your time on it as you do in uni.
reply
100%! I learned so much at a really high rate, I'll never ever have the time and focus to do that again, most probably. It felt really good to dig deep
reply
That, and some subjects are really hard to learn at home/at job. Learning Linear algebra at home would be really hard, but learning some new programming language would work fine.
reply
why is learning linear algebra at home hard?

no knowledge of this area, hence asking.

reply
Yes, this is so true. Too many people just want the immediately useful information, but this is not what universities is for! In Uni we should learn things that can be relevant decades later. Not just learn the most modern tools that is currently used in industry. It should be coupled with that too, but not only. The short 2 year educations to learn CS basics are kind of like the fast food of learning. It gets you there, but something is missing.
reply
No people want to get a job so they can make money to exchange for goods and services. First they need to be able to support their addictions to food and shelter.

Companies are looking for people who can immediately improve their bottom lines. Why hire someone out of college with no practical skills when they can hire someone for slightly more that already has practical skills?

reply
It depends on your time scale.

As an employer we're not just looking for someone to fill a role now, we're considering the person's potential to grow and move onto more challenging roles.

As an employee money is clearly a driving factor, but other things also impact quality of life. Working conditions, work-life-balance, annual leave, scope for advancement, company structures etc all make a difference.

Yes money matters, but if you choose only based on that you end up in places where people (co workers and managers) only care about money. YMMV.

reply
The average tenure of a software developer is 3 years. This is mostly because of salary compression where internal raises never keep up with the market and new hires come in making more than “loyal” employees. Companies don’t invest in their employees.

I’ve seen this personally in companies that had 20 people all the way to the US’s second largest employer. Not to mention, it’s much easier to get a promotion by changing employers than going through the internal promo process.

Unless you are working for a non profit, everyone mostly cares about money. Any halfway competent interviewee knows how to fake “passion about the mission”

I’m 50 now and I do value things more than money about my company. An equivalent position to what I have now pays 30%-40% more at AwS (been there done that) or GCP (I’ve turned down recruiters and managers). But I value autonomy, my real usable unlimited PTO, having influence on the company direction, work life balance etc.

I can make those choices. When you are young and just starting out you can’t and honestly you shouldn’t.

reply
Thank you. Yeah, I would do Comp Sci. I wont say that I know everything about software development. Not even close, but I do think I'm in a position where I have the ability to continue to learn on my own. I mostly want the paper, but I'd be lying if I said I couldn't stand to drastically improve my CS fundamentals. Most of what I do is Typescript/Javascript, but I'm also into embedded development, for which I'm way less advanced at. I could really use some lower level training.
reply
Do note that at least for me, we didn't do much coding or software engineering. I spent more time on proofs, theories and writing on paper than any code. The best I could describe it is that software engineering is kinda adjacent to compsci maybe? I think you can do more applied compsci and do stuff like embedded etc. and it might be different, I started uni 15 years ago
reply
Community college near by probably has comp architecture and assembler classes, which fill out the low level knowledge.
reply