By far the best teacher I've seen in last 5 years. I'm lucky that youtube recommended this channel to me a couple of months ago. I'm sure you'll become even more successful. Thank you!
Can u make a video on react folder structures with some multi roles dashboard examples, as that can explain the feature folder structure better. also can u suggest 2-3 opensource libraries for better folder structure.
Really helpful video! It would be great if you can make a video on how to estimate the project timeline when a new requirement comes up from the client especially for senior people.
Regarding point 7, very well put. But it's best if you have at least 1 TS wizard on your team. You need good direction. And every once in a while there's that generic or mapped type that can make things type-safe & boilerplate-free at the same time, and it takes a bit of skill to recognise opportunities for and implement those. On the other hand, what I have witnessed in one company was a TS codebase full of `any` and `as` as well as explicit type annotations everywhere (to stop the `any` from propagating) and repeated declarations of very similar types (because people didn't hear about things like `Pick` or `Omit`). The team seemed to think TS is just putting type annotations everywhere and that it makes things somehow better.
I don’t understand why point 5 is controversial. Something should be reusable only if you actually need to reuse it. Even in that case, in my previous job we followed the Rule of 3. Meaning you extract code and make it reusable only the 3rd time you need it. This is not a react-specific thing, it’s a general design principle which makes total sense.
In my experience (not just with react) this is one of the biggest root causes of long term software rot-based issues. Starting with forced abstractions is an absolute anti pattern
Thank you for this cool tips ❤ I'm learning react as my frontend and c# as backend to become a Full Stack Dev. When creating a new project I'm always struggling with making a good looking design (but I'm not a designer) and essentially ask AI to make me one. Can you tell me should I even try to think of a good design or design from AI is perfectly fine? P.S. I know CSS syntax very well. I just cannot create a picture of cool design to make
You can pick nice designs from other sites like Pinterest. My life as dev is hard enough to be concerned with design. There are people way more talented thinking about that.
Very very good tips ❤❤. I have a question. In simple app I want to use my custom hook instead react query but the problem I have is the dependency array, how can I safely use my custom hook like useEffect ?
Yes as an a junior React developer, I just realize, at first I made every component is too reusable, even just a Card component. It become too complex and make it harder to read.
Regarding point 10, yes, you do quality content. I'm a senior backend dev, so I can smell BS from a mile away, and your content is the opposite of that :)
Regarding point 3, I used to have a few violations in my code like so: ```ts function useSomething() { const { type } = useAppSettings(); if (type === 'abc') { useEffect(...); } ... } ``` It worked, because `type` would never change between re-renders. But I guess it would throw off the React compiler, right? Anyway, I refactored away from code like this, just because I didn't like the smell.
there's a duplicated 2 different scenes when representing 10th tip ) I don't understand which was inappropriate and you didn't want to add in the video )
TypeScript tries to turn JS into something it's not, therefore it's unnecessary and in many cases counter productive. Write clean code, know how to debug and you won't ever need TS.
11 and the most importan: keep it simple, 12: do anything you possibly can in the backend (business logic), frontend is just for rendering UI.
13. Use htmx
What? frontend is just for rendering UI? you should stop smoking cocaine.
By far the best teacher I've seen in last 5 years. I'm lucky that youtube recommended this channel to me a couple of months ago. I'm sure you'll become even more successful. Thank you!
Can u make a video on react folder structures with some multi roles dashboard examples, as that can explain the feature folder structure better. also can u suggest 2-3 opensource libraries for better folder structure.
You’re my fav react teacher. Would love to know the senior dev stuff you learnt from Wordpress.
Really helpful video! It would be great if you can make a video on how to estimate the project timeline when a new requirement comes up from the client especially for senior people.
Regarding point 7, very well put. But it's best if you have at least 1 TS wizard on your team. You need good direction. And every once in a while there's that generic or mapped type that can make things type-safe & boilerplate-free at the same time, and it takes a bit of skill to recognise opportunities for and implement those. On the other hand, what I have witnessed in one company was a TS codebase full of `any` and `as` as well as explicit type annotations everywhere (to stop the `any` from propagating) and repeated declarations of very similar types (because people didn't hear about things like `Pick` or `Omit`). The team seemed to think TS is just putting type annotations everywhere and that it makes things somehow better.
I learnt a lot about generics but didn't know about mapped types. Thank you for writting that, I'll start studying mapped types.
You provide best quality content and learning many things from you. Thank you.
Thanks so much brosky. Always positive
what are some good open source e=react code bases to refer?
Great tips, thank you and yes i do agee, you have the most quality content on React among many youtubers i know of, keep it up.
14:34 lil glitch in the edit ? 😄
I don’t understand why point 5 is controversial. Something should be reusable only if you actually need to reuse it. Even in that case, in my previous job we followed the Rule of 3. Meaning you extract code and make it reusable only the 3rd time you need it. This is not a react-specific thing, it’s a general design principle which makes total sense.
In my experience (not just with react) this is one of the biggest root causes of long term software rot-based issues. Starting with forced abstractions is an absolute anti pattern
Great, it's always good to reset yourself with these principle and avoid those deep rabbit holes. Thanks
Thank you for this cool tips ❤
I'm learning react as my frontend and c# as backend to become a Full Stack Dev. When creating a new project I'm always struggling with making a good looking design (but I'm not a designer) and essentially ask AI to make me one. Can you tell me should I even try to think of a good design or design from AI is perfectly fine?
P.S. I know CSS syntax very well. I just cannot create a picture of cool design to make
My same problem
You can pick nice designs from other sites like Pinterest. My life as dev is hard enough to be concerned with design. There are people way more talented thinking about that.
can you maje video guide on feature based folder structure or if there is a open source project please link it in comment
What do you think of Apollo Client instead of using React Query?
Quality content. Thank you.
valuable tips, thanks
Very very good tips ❤❤. I have a question. In simple app I want to use my custom hook instead react query but the problem I have is the dependency array, how can I safely use my custom hook like useEffect ?
Yes as an a junior React developer, I just realize, at first I made every component is too reusable, even just a Card component. It become too complex and make it harder to read.
Regarding point 10, yes, you do quality content. I'm a senior backend dev, so I can smell BS from a mile away, and your content is the opposite of that :)
Thanks ❤️
Thanks sir ❤
I think I know which channel to watch for tip #10 😉
Regarding point 3, I used to have a few violations in my code like so:
```ts
function useSomething() {
const { type } = useAppSettings();
if (type === 'abc') {
useEffect(...);
}
...
}
```
It worked, because `type` would never change between re-renders. But I guess it would throw off the React compiler, right? Anyway, I refactored away from code like this, just because I didn't like the smell.
there's a duplicated 2 different scenes when representing 10th tip ) I don't understand which was inappropriate and you didn't want to add in the video )
Nice
10th tip came in twice
Bad advice to import components from one feature to another.
Not really, e.g. Posts card needs user avatar from users feature
TypeScript tries to turn JS into something it's not, therefore it's unnecessary and in many cases counter productive. Write clean code, know how to debug and you won't ever need TS.
you said '"know how to debug". that's what we use typescript for.
@@kazmi401 if you need TS to debug effectively, you're not writing good code.
Ten great tips for all React Developers. Thanks, Darius.
{2025-01-31}