Man! What a video! You taught "Redux and SSR ReactDOMServer" in just 10 minutes! Such a nice simple example and made me to understand easier and now confidence to learn them in detail. Thanks a lot. 1st video of urs from me, direct sub, direct respect, direct inspiration. Long live with all you wish, dude! Thanks a ton.
I've been watching lots of react interview prep videos, and the only question this one shares is the first one. Thanks for the good practice questions.
Thank you for sharing your experience and knowledge, your explanation was awesome 🎉 I’ve been working in React and you give a really nice insights to consider in our future projects.
11:38 It's opinionated, not optionated; Opinionated in terms of redux means the library comes out to ensure that everyone is using the library the same way. This ensures that people aren't doing whatever they want when implementing redux in an app, which makes it significantly easier to learn and enjoy.
Great content, amigo!! What addon are you using for hiding the other lines in Code? I think it's a good idea so we can just focus on the logic. Cheers!!
If you have a button that opens a popup menu, you might not want the popup to be rendered directly within the same DOM hierarchy as the button. This is particularly useful for avoiding potential issues with styling, z-index conflicts, or DOM hierarchy constraints. In such cases, you can create a reusable Popup component that uses React.createPortal to render its content outside the parent component's DOM tree-typically directly into a dedicated root element (e.g., a div with id="portal-root"). By doing this, the popup can still maintain its logical association with the button (e.g., positioning it below the button using the provided anchor as a prop) while being decoupled from the DOM hierarchy of the button. This approach can be used for a variety of UI components beyond dropdowns, such as modals, tooltips, notifications, or any overlay elements.
Hats off to you, dude. I've been meaning to brush up on the “lazy loading vs code splitting” and your video helped tremendously to tell them apart. Basically, to “lazy load” something, that portion of code needs to be “split” by our bundler. That way, that small .js file is decoupled from the initial bundled app and can later be “Lazy loaded” on demand. Thanks for helping make the distinction more easily 🙌🏻
Just to complement: Lazy loading is not just about code splitting itself, but all techniques that involves defering the load of something. I'm saying that just because you can, for example, lazy load images of a page. And in this case you don't need to split anything, but just get scrolling behavior and then requesting the images, you know?
@CoderOne Thanks for very precise explanation. I really like your VS code settings. :) Can you maybe share your configuration for IDE? and used plugins. Thanks and keep up the good work!
a fair question. in the interview are you suppose to code a full redux without chekcing docs? I think redux is so much boilerplate to be asked in a interview without permission to check the docs
Man! What a video! You taught "Redux and SSR ReactDOMServer" in just 10 minutes!
Such a nice simple example and made me to understand easier and now confidence to learn them in detail. Thanks a lot. 1st video of urs from me, direct sub, direct respect, direct inspiration. Long live with all you wish, dude! Thanks a ton.
I've been watching lots of react interview prep videos, and the only question this one shares is the first one. Thanks for the good practice questions.
Wow! This was delightful to watch. Great and to the point!
Thank you. what is the VS code plugin name that minimize the tailwind classes?
want to know too
@@carlogiovanni1362 btw the extension name is "Tailwind Fold"
Tailwind fold
@@carlogiovanni1362 Tailwind fold
Thank you for sharing your experience and knowledge, your explanation was awesome 🎉 I’ve been working in React and you give a really nice insights to consider in our future projects.
11:38 It's opinionated, not optionated; Opinionated in terms of redux means the library comes out to ensure that everyone is using the library the same way. This ensures that people aren't doing whatever they want when implementing redux in an app, which makes it significantly easier to learn and enjoy.
For the second question, what are some use cases for rendering elements outside of the component tree?
if they ask about prop drilling, use contexts/provider relationship pattern!
Great content, amigo!! What addon are you using for hiding the other lines in Code? I think it's a good idea so we can just focus on the logic. Cheers!!
when and what should I choose ref or getElementbyID for selecting html element . I always use ref for element but is there any side effects ?
great video, thank you
For what particular tasks should we use react portal?
I have no idea it exists until now.
If you have a button that opens a popup menu, you might not want the popup to be rendered directly within the same DOM hierarchy as the button. This is particularly useful for avoiding potential issues with styling, z-index conflicts, or DOM hierarchy constraints.
In such cases, you can create a reusable Popup component that uses React.createPortal to render its content outside the parent component's DOM tree-typically directly into a dedicated root element (e.g., a div with id="portal-root").
By doing this, the popup can still maintain its logical association with the button (e.g., positioning it below the button using the provided anchor as a prop) while being decoupled from the DOM hierarchy of the button.
This approach can be used for a variety of UI components beyond dropdowns, such as modals, tooltips, notifications, or any overlay elements.
Hats off to you, dude. I've been meaning to brush up on the “lazy loading vs code splitting” and your video helped tremendously to tell them apart.
Basically, to “lazy load” something, that portion of code needs to be “split” by our bundler. That way, that small .js file is decoupled from the initial bundled app and can later be “Lazy loaded” on demand.
Thanks for helping make the distinction more easily 🙌🏻
Glad it helped ^^
Just to complement:
Lazy loading is not just about code splitting itself, but all techniques that involves defering the load of something.
I'm saying that just because you can, for example, lazy load images of a page. And in this case you don't need to split anything, but just get scrolling behavior and then requesting the images, you know?
what extension allows youi to see file size on the first line?
last one was gold. but i think it won't ask in an interview
@CoderOne Thanks for very precise explanation. I really like your VS code settings. :) Can you maybe share your configuration for IDE? and used plugins. Thanks and keep up the good work!
Thanks a lot
great
Zustand is the literal translation ''State" from German
pls make more video like this
Wonder how you didn't even mention context API, react built-in as just an option for fourth question
I see bun I automatically like the video.
a fair question. in the interview are you suppose to code a full redux without chekcing docs?
I think redux is so much boilerplate to be asked in a interview without permission to check the docs
Something wrong with video keeps crashing
Theme?
That's great info can you provide me github link ?
BRO EXPLAINED PERFECTLY REDUX IN 5 MINUTES 💀💀💀💀💀💀
plz provide code of this question
No. You lazy
bro you need to enunciate your words
Whoever asks these questions in an interview is a psycho!
why? as a professional react developer, I can tell these questions're good.
@@vaskogood1580 to ask an entry leve or junior some of these questions are crazy.
Thank you!