Learning by doing is obviously the best way, but not every role has that kind of opportunity. You can build something on the side and scale it, but it's easier

Learning by doing is obviously the best way, but not every role has that kind of opportunity. You can build something on the side and scale it, but it's easier to just do that in a company :) I'm no expert on system architecture, but I have noticed that reading a lot of docs and blogs on how other companies do things successfully has helped me: Quastor: quastor.org - Engineering blog posts and summaries Engineer's Codex: read.engineerscodex.com - Case studies and summaries of Big Tech systems and software architectures SWE Quiz: swequiz.com - Bunch of useful questions that has helped me a lot at work TLDR Web Dev: tldr.tech/webdev - Good for keeping up on engineering-specific stuff in general. I have a Feedly set up with these blogs too: https://blog.bytebytego.com/p/79-engineering-blogs-to-level-up https://blog.bytebytego.com/p/79-engineering-blogs-to-level-... ByteByteGo is good too, though that's an obvious one that everyone already knows about.