Comments by "Ozzy Perez" (@OzzyTheGiant) on "NeetCode" channel.

You just read them. This might not be for everyone. Usually, if you already have experience with other frameworks, what you do is you look for similar patterns for how to do something in the tool you want to learn. For example, if you want to learn Svelte coming from Angular, you might say "I can create props in Angular by annotating a property in a component with @Input, so what's the equivalent in Svelte?", turns out you can just do "export let myProp: string = 'test'" and you have a prop just like in Angular. Just find the way of doing things in Svelte as you would do them in the framework you would do them. Otherwise, if you're new to frameworks, start from the ground up and go through each page understanding what all the main concepts are for building components.
2
@NeetCode I think with Docker, unless you specifically want to get into DevOps roles, most of the time you just need to learn the basic commands and how docker-compose works, as you will mainly just spin up containers and ensure they're running during development.
1
SvelteKit all the way. This is the kind of thing that I've been saying that, if you have any leverage in what stack to pick, adopt Svelte. Drop React, it's just a mess of a framework at this point; we need to drive adoption for Svelte. Also advocating for Go. It's one of the simplest back end languages you can learn with strong typing and AOT compilation. It can output small binaries to your platform of choice and you can even embed static files inside such binaires, which makes deployment so much easier. No more cluttering your servers with node_modules. Plus Go is great for concurrency and performing CPU intensive tasks on separate goroutines. Because of this, I feel like Go scales far better than node.js. The only time I choose TS for back end is if I have dozens or even hundreds of data models I need to share between the front and back end, which is almost never. Lastly, if you want to get into cross platform mobile and desktop development, look into Flutter. It's very straightforward and has a great set of UI components.
1
Is it as difficult as some people say it is? I'm gonna assume that if you are great at solving problems in code, things like differential equations should not be as difficult, but I could be wrong
1
And it's framework agnostic, like Tailwind, so you can take it to any JS framework you want
1
Yeah, it basically boils down to the builder returning itself after every method, until you reach a final method that returns an instance or something else
1
As much as I'm starting to hate the JS ecosystem, I'm glad people are at least using TypeScript for a better workflow and cleaner code.
1