Hacker News new | ask | show | jobs
by 908B64B197 2024 days ago
It's a good recap but it's all things I expect a college grad to just know or be able to grok pretty fast.

Also why not Google?

1 comments

I'm just not there from a skills perspective. I feel like being a SRE at Google is the top of the food chain which I'm no where near.

Not trying to bring myself down but trying to be realistic :)

Unless you already know this really well, I'd start even at a more fundamental level than what is suggested by LinkedIn. I'd try learning Unix and a little bit of C by using The Unix Programming Environment by Kerninghan & Pike plus Kerninghan & Ritchie. It's quite timeless. Files, pipes, pointers, etc. That's the plumbing of software engineering.

Then also learn the calculus of software engineering: Logic. A good short intro is Huth & Ryan. The book covers some advanced topics in later chapters, but you don't need that if you don't want to. Logic is also timeless, and very practical. You can gain the ability to model check things, which is really really cool and used pretty often for e.g. distributed systems. This can unlock many cool positions for you.

Logic can also take you to logic and declarative programming. Something also worth investing into, and pretty addictive. For that, there's nothing better than The Art of Prolog.