That's very reassuring that I'm on the right track. I do generally choose projects and studying that interests me, or is at least a doorway to something that interests me. You've also reminded me to shift my perspective a bit toward curiosity and away from obligation, which is often enough to get something kickstarted. There is indeed always something to learn on any project that's interesting and will build toward deeper knowledge. Thanks for your insights!

Hi Brian! Thanks for taking the time to do an AMA! My question is coming from the perspective of an intermediate dev who'd like to be senior someday. With the rapid growth and change across the stack, I find it hard to feel invested in learning one framework over another when in a few years time the landscape could look completely different. I'm concerned that large chunks of my hard-earned knowledge will become outdated. The answer to that concern is often "focus on the foundations" (languages, stuff like APIs, and CompSci concepts) which is admirable, but not necessarily helpful when job searching, especially early in your career. Most of us are crunched for study time, as well, so it's good to be smart about where you put your focus. What are your thoughts on frameworks vs foundations and how to balance staying current but also thinking long term in the current industry?