Try to stay in a learning mentality, anything you find yourself needing to learn is awesome. You'll crave for that later, because you'll know too many technologies and you'll miss the hunt for knowledge. Follow all your interests or opportunities, each one will give you an advantage in your next tech project. Stack em up.

IMO, the best devs I've ever worked with, have just seen more issues than the next. Having "been there before" is a huge advantage.

Syntax retention, I personally have found that it's most sticky when my fingers tippity tapped out code, but it's THE MOST sticky when I run into a bug or I used it wrong.. So the idea here is that the more problems you've had the opportunity to see and solve, the stickier all of it becomes.

am never satisfied with how it looks You're not alone. Do your best to distinguish between your own opinions and time spent with the design, and whether or not there's actually problems. And just know that the person who made that perfect design, is probably over it already. They just beat you to it. Your favourite tools/extensions you use while developing Chrome and Firefox Devtools + VisBug

How's Google Chrome team handling the current pandemic crisis? We are deploying people and services to governments, to teams managing unemployment services, etc. How are you guys working these days? We were fairly remote before, so this isnt so bad. We work async. Lots of emails, github issues/comments, and meetings when we need them. What rules do you all follow to stay productive during the lockdown? No one is babysat. Each person is going to manage their own work life balance.

Chrome DevTools VisBug Terminal (no, i dont use any of the plugin / moddable terminals)(i've used them a ton, but found that I needed to be savvy without the helper plugins, for all the times i'm remoted into a server.) Every browser (i keep all of them installed and ready to QA) Simulators and Emulators (gotta test!) Real devices Github Desktop for most of my git workflows Screenflow Adobe XD and Figma Sublime or Code Kap (if you make UI and want to showcase it) Insomnia (testing apis) Android Studio and Xcode Typora for markdown notes

Here's my desired flow: Empathize Define Design Develop Deploy There's parts in here where you cycle back to previous steps. But this is it in a high level, and I've seen it work really well across lots of product types and team sizes.

Build stuff. Fastest way to learn to code, isn't to read or watch people do it, it's to go solve problems, in whatever way you can. Then do it again and again. 1 project (that you complete) is worth a whole 10 weeks of classroom time. Furthermore, the more passion and attention to detail you put into it, the more you learn the real day to day tasks required to make apps/sites. Most "education content" is so fluffy and stripped down to the succinct presentation, that it's not realistic and can create false expectations about the difficulties. Make stuff! Make more stuff! Step back and evaluate where you spent time and were interested, then go dig deeper into that! And if you need external influence to feel motivated, join an open source project or ping friends and start something. Even if it's a dumb app like "who's got who's video game."

Both are capable of supporting a project and ultimately wont be a reason you succeed or fail as a product/business/team.

learn both. it's not like "pick a sword or an axe" to study as a ninja. dont think one is superior. don't think you can get away with only learning 1. grid is better for grids and flex for constraint and autolayout strategies. both have features the other doesnt, both have features the other does. it's case by case, and the right tool will manifest itself while your testing and trying against your real content. biggest tip: strive to understand both for yourself, make them both weapons in your arsenal of layout, you'll need them.