Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

_georgemoller's profile picture

George Moller

119,046 subscribers

177,601 görüntüleme • 2 yıl önce •via X (Twitter)

KomediBilim & TeknolojiEğitim
LIVE

Anya Rossi• Live Now

Private livecam show

10 Yorum

George Moller profil fotoğrafı
George Moller2 yıl önce

Hey there 👋 Friendly reminder that I have more than 100 infographics and video animations just like this one. Check them out ↓

George Moller profil fotoğrafı
George Moller2 yıl önce

Hey there 👋 Friendly reminder that I have more than 100 infographics and video animations just like this one. Check them out ↓

Hammad Ahmad profil fotoğrafı
Hammad Ahmad2 yıl önce

noice , ok what if we get data from an Api call , then , we first loop all the array of object to store ids and entities, then we will again loop over the data , and then time completely will be O(n2) . i mean really? correct if i am wrong 😑 .

George Moller profil fotoğrafı
George Moller2 yıl önce

@ch_hadi0 Data should already come normalized from the API backend

mvrlin profil fotoğrafı
mvrlin2 yıl önce

What’s the point of having ids and entities? Now you have O(n^2) space complexity. Just use plain object or even better Map.

Pavel Romanov profil fotoğrafı
Pavel Romanov2 yıl önce

I’ve seen such things in a wild and sometimes it can really boost your performance! The only thing I would change is to convert “users” to the Map. I’ve found it really useful lately

Vojtěch Jedlička profil fotoğrafı
Vojtěch Jedlička2 yıl önce

This doesn't make much sense to me. 1. Map is designed to do exactly this. 2. There is no noticeable performance difference for smaller than huge arrays and those should be paginated anyways.

George Moller profil fotoğrafı
George Moller2 yıl önce

Not for smaller arrays, but try measuring the performance of the find method against the map when you have thousand of entries/records and you'll see a notable difference.

ricklove profil fotoğrafı
ricklove2 yıl önce

No, don’t introduce complexity. Lookups should only be used inside an algorithm with a loop. Code review failed.

RadicalRabbit profil fotoğrafı
RadicalRabbit2 yıl önce

Why is a seperate array of just ids needed?

Benzer Videolar

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

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

George Moller

152,253 görüntüleme • 1 yıl önce

❌ Avoid deriving state in useEffect in React, this can create multiple unnecessary render phases. ✅ Instead derive the state directly in the event handler, this way you'll have one single render phase. ↓
0:29

❌ Avoid deriving state in useEffect in React, this can create multiple unnecessary render phases. ✅ Instead derive the state directly in the event handler, this way you'll have one single render phase. ↓

George Moller

33,474 görüntüleme • 1 yıl önce

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

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

George Moller

177,627 görüntüleme • 1 yıl önce

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

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

George Moller

130,061 görüntüleme • 2 yıl önce

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

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

George Moller

137,429 görüntüleme • 2 yıl önce

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

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

George Moller

48,311 görüntüleme • 1 yıl önce

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

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

George Moller

124,069 görüntüleme • 2 yıl önce

A big mistake I see people routinely making is NOT clearly defining a time horizon prior to an investment/trade. Your time horizon for a trade is dictated by the longevity of the variables that trigger price action. i.e. $BTC is a long term hold due to the debasement of fiat + passive ETF bid over time (the variables here take years to play out) The same can be applied to a short term trade (the variables could be fast-moving). Full thoughts below.
2:31

A big mistake I see people routinely making is NOT clearly defining a time horizon prior to an investment/trade. Your time horizon for a trade is dictated by the longevity of the variables that trigger price action. i.e. $BTC is a long term hold due to the debasement of fiat + passive ETF bid over time (the variables here take years to play out) The same can be applied to a short term trade (the variables could be fast-moving). Full thoughts below.

Miles Deutscher

52,180 görüntüleme • 1 yıl önce

Increasing smart contract complexity → greater oracle demand → more usage of the Chainlink platform
4:43

Increasing smart contract complexity → greater oracle demand → more usage of the Chainlink platform

Chainlink

26,307 görüntüleme • 6 ay önce

Don’t waste time creating manual styles and variables in Figma!
0:24

Don’t waste time creating manual styles and variables in Figma!

Jan Mraz

17,169 görüntüleme • 8 ay önce

Introducing Variables! (Beta)🔸A new way to create interactive experiences in Spline. 🤹‍♀️ Numbers, Strings, Booleans 🔥 Dynamic: Time, Counter, Random ↔️ Attach variables to inputs ⚡️ Trigger events from variables 🎯 Capture object props changes Demo: Remix:
0:48

Introducing Variables! (Beta)🔸A new way to create interactive experiences in Spline. 🤹‍♀️ Numbers, Strings, Booleans 🔥 Dynamic: Time, Counter, Random ↔️ Attach variables to inputs ⚡️ Trigger events from variables 🎯 Capture object props changes Demo: Remix:

Spline

85,390 görüntüleme • 2 yıl önce

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

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

George Moller

120,828 görüntüleme • 2 yıl önce

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

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

George Moller

256,599 görüntüleme • 2 yıl önce

You should stop using environment variables. They are a horrible untyped and unsafe mutable global state. A ticking time bomb. Even Rust can't save you.
22:22

You should stop using environment variables. They are a horrible untyped and unsafe mutable global state. A ticking time bomb. Even Rust can't save you.

Valentin Ignatev

71,524 görüntüleme • 5 ay önce

working with a combination of variables, modes, base components, and themed instances to explore designs in light and dark mode at the same time 🔊
0:32

working with a combination of variables, modes, base components, and themed instances to explore designs in light and dark mode at the same time 🔊

David Hill

18,858 görüntüleme • 7 ay önce

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

❌ 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,781 görüntüleme • 2 yıl önce

📢Our #CopernicusClimate Change Service has recently released the "#Copernicus Interactive Climate Atlas" (C3S Atlas) It allows to explore 30 climate variables through 8 state-of-the-art datasets More at
1:07

📢Our #CopernicusClimate Change Service has recently released the "#Copernicus Interactive Climate Atlas" (C3S Atlas) It allows to explore 30 climate variables through 8 state-of-the-art datasets More at

Copernicus EU

22,802 görüntüleme • 2 yıl önce

Component properties can now be bound to variables Also, UI has been simplified so that props and variables are in the same dropdown
3:23

Component properties can now be bound to variables Also, UI has been simplified so that props and variables are in the same dropdown

Figma

38,480 görüntüleme • 1 yıl önce

(1 of 5, a thread) Assembling an expression through a series of bite-size clips, slowly increasing in complexity of tool use. To start, creating a simple subtle smile by moving just the upper center and corner lip "A" bones, using only position along a single axis at a time:
1:10

(1 of 5, a thread) Assembling an expression through a series of bite-size clips, slowly increasing in complexity of tool use. To start, creating a simple subtle smile by moving just the upper center and corner lip "A" bones, using only position along a single axis at a time:

Catte Next Door

127,429 görüntüleme • 1 yıl önce

Found a dream plugin for making typography scales, it creates: – Variables – Styles with variables as values – Sticker sheet on the canvas And you can build ramps based on a ratio/calculation as well, saving a tonne of time
1:46

Found a dream plugin for making typography scales, it creates: – Variables – Styles with variables as values – Sticker sheet on the canvas And you can build ramps based on a ratio/calculation as well, saving a tonne of time

luis.

49,425 görüntüleme • 1 yıl önce