Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

❌ Avoid deeply nested validations that are hard to read. ✅ Instead use invariants.

George Moller

117,957 subscribers

207,021 views • 2 years ago •via X (Twitter)

Science & Technology Education Comedy

Anya Rossi• Live Now

Private livecam show

10 Comments

George Moller2 years ago

I've been working professionally with React and JavaScript for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video tutorials just like this one. Check them out ↓

PATRYK2 years ago

Don’t follow this advice. It makes your code less readable, it confuses other developers and your IDE. This level of abstraction is not helping anybody. Just use early return.

Vlad Tansky2 years ago

Nice, but wouldn’t it be easier to read code with if(!condition) throw new Error(“some message”) Instead of creating abstraction?

xavi2 years ago

Just use fail fast/ early return and you’ll avoid that level of abstraction.

dcodes 🦀2 years ago

just use zod

Hamilton Greene 🐷🦔2 years ago

I don't like this - you're hiding important control flow inside deeply nested functions. The caller must now know that implicitly your functions use exception control flow and throw on certain conditions (also hidden). Guards (if not x return) are usually better.

Remus2 years ago

Dude an "any" wrapper function? That's scares the shit out of me

Proziam2 years ago

I have to know, what are you using for the animations and graphics? Looks clean

Ndeye Fatou Diop 🚢 💻 | DEV | 🇸🇳🇫🇷2 years ago

💯 This makes it super hard to read the code

Seve2 years ago

"early bail" or "early return" is far better terminology

Related Videos

❌ Avoid difficult-to-read conditionals to render elements in react. ✅ Instead use utility components for conditional rendering.

❌ Avoid difficult-to-read conditionals to render elements in react. ✅ Instead use utility components for conditional rendering.

George Moller

301,147 views • 3 years ago

❌ Avoid difficult-to-read conditionals in React. ✅ Instead you can use ts-pattern to express complex conditions in a single, compact expression.

❌ Avoid difficult-to-read conditionals in React. ✅ Instead you can use ts-pattern to express complex conditions in a single, compact expression.

George Moller

185,805 views • 3 years ago

❌ Avoid multiple state variables to track status. ✅ Instead use enums.

❌ Avoid multiple state variables to track status. ✅ Instead use enums.

George Moller

152,399 views • 1 year ago

❌ Avoid prop-drilling your components to extend them ✅ Instead use composition

❌ Avoid prop-drilling your components to extend them ✅ Instead use composition

George Moller

51,316 views • 8 months ago

❌ Don't pass props to multiple nested components in React. ✅ Instead use libraries like react-query to better handle server state.

❌ Don't pass props to multiple nested components in React. ✅ Instead use libraries like react-query to better handle server state.

George Moller

137,443 views • 3 years ago

❌ Avoid using useState for more complex state management ✅ Instead use useReducer ↓

❌ Avoid using useState for more complex state management ✅ Instead use useReducer ↓

George Moller

124,086 views • 3 years ago

❌ Avoid using objects as dependencies in React.useEffect() ✅ Instead use the primitive keys

❌ Avoid using objects as dependencies in React.useEffect() ✅ Instead use the primitive keys

George Moller

43,042 views • 1 year ago

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

George Moller

130,080 views • 3 years ago

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

George Moller

177,710 views • 2 years ago

❌ Avoid listening for ref changes with useEffect() in React. ✅ Instead use a ref callback function.

❌ Avoid listening for ref changes with useEffect() in React. ✅ Instead use a ref callback function.

George Moller

101,654 views • 3 years ago

❌ Avoid mixing business logic with your React components. ✅ Instead create abstraction layers that communicate with them.

❌ Avoid mixing business logic with your React components. ✅ Instead create abstraction layers that communicate with them.

George Moller

214,976 views • 3 years ago

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

256,697 views • 3 years ago

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

120,910 views • 2 years ago

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

George Moller

48,354 views • 2 years ago

❌ Don't disable ESLint warnings in useEffect ✅ Instead use useEffectEvent from React 19.2

❌ Don't disable ESLint warnings in useEffect ✅ Instead use useEffectEvent from React 19.2

George Moller

57,450 views • 9 months ago

We got you covered 🤝 Can Tell us what teams to avoid ❌ Use code “Welcome” for 15% off ✅ 🛒 Order now -

We got you covered 🤝 Can Tell us what teams to avoid ❌ Use code “Welcome” for 15% off ✅ 🛒 Order now -

Mystery Champions

69,700 views • 2 years ago

❌ Avoid increasing time complexity by having non-normalized state variables in React . ✅ Instead normalize the structure of the state variables to reduce time complexity.

❌ Avoid increasing time complexity by having non-normalized state variables in React . ✅ Instead normalize the structure of the state variables to reduce time complexity.

George Moller

177,625 views • 3 years ago

🚨UPAMECANO TOTY FLASHBACK REVIEW🚨 ✅Use Tah instead🇩🇪 Final verdict: CLEAR SKIP❌

🚨UPAMECANO TOTY FLASHBACK REVIEW🚨 ✅Use Tah instead🇩🇪 Final verdict: CLEAR SKIP❌

FUT Coin Shop

29,239 views • 8 months ago

❌ You 𝗺𝗶𝗴𝗵𝘁 not need a react form library ✅ Instead you can use the FormData API's

❌ You 𝗺𝗶𝗴𝗵𝘁 not need a react form library ✅ Instead you can use the FormData API's

George Moller

81,577 views • 3 years ago

❌ Adding state to useCallback dependencies. ✅ Instead, use functional setState. Stable callbacks, no stale closures, no unnecessary re-renders. Here's the pattern ↓

❌ Adding state to useCallback dependencies. ✅ Instead, use functional setState. Stable callbacks, no stale closures, no unnecessary re-renders. Here's the pattern ↓

George Moller

17,264 views • 9 months ago