Closed craigmaloney closed 7 years ago
Give up? :)
That's currently where I'm at, but I'd rather give it another shot.
But seriously, I think a progression is a good idea:
The main thing, though, is to get past choice paralysis and just play with some things. You won't master all the frameworks that exist today—and even if you totally threw yourself at them, you'd find about half of them were dead by the time you figured things out. But, a lot of them today share enough common attributes that you can more easily accumulate the gist of modern patterns iteratively. So, even if you pick one, and it dies, you haven't really wasted your time in trying another one—you'll have a good head start
Oh, and node is pretty fun. I've found "isomorphic" apps where server & client share most code to be less convenient and more tedious than one might hope, but it's nice to at least stick around in one language for a project. And modern build chains let you share a lot of the utility code modules at least.
Thank you.
I've been working my way through "Eloquent JavaScript" and "Understanding ECMAScript 6". Is there another book / resource you'd recommend for doing more VanillaJS development? (The Mozilla Site looks like a great resource as well).
Honestly, I haven't had much use for tech books in awhile. I like MDN, but then I helped build it for awhile so I'm biased :grin: There are some good live examples to tinker with there, though.
Also for staying relatively up-to-date at least on buzzwords & trends, I've gotten a lot of use out of Node Weekly and JS Weekly email newsletters. The Hacks blog at Mozilla can also be handy for keeping tabs on new things. Also random assorted podcasts, like JavaScript Jabber (trying to think of more)
Cool. Thank you!
Otier than "Panic". :)