3 ms·
I see this all the time. Every single engineer starts off thinking "What should I study?". IMO, it's the wrong question. Study whatever you want, it doesn't re
by staticassertion 6y ago
I see this all the time. Every single engineer starts off thinking "What should I study?".
IMO, it's the wrong question. Study whatever you want, it doesn't really matter. Get a lot of breadth, that's fine.
But go deep somewhere. How? Do a project! Something interesting, something you can't do today, and something you want to do. And don't stop. You'll hit walls, just ask people for help, find communities where they'll help you through it, read docs.
Even if you fail, so long as you really push yourself, you'll learn a ton. And soon you'll know which projects are "tough but possible" a lot better.
It's a meme at this point that developers have 1000 different projects they never finished. Don't worry about that. In my experience it's because about 75% through a project you hit a point where it stops being fun, you stop learning things, and now it's just doing the work to wrap it up, which can be a lot less valuable.