I initially found it challenging to determine when to use memoization. However, I’ve learned that it’s particularly useful when dealing with overlapping subproblems—situations where the same calculations are repeated multiple times. #algorithms - ThreadSky

About ThreadSky

maiproject218.bsky.social • 20 days ago

I initially found it challenging to determine when to use memoization. However, I’ve learned that it’s particularly useful when dealing with overlapping subproblems—situations where the same calculations are repeated multiple times.
#algorithms

Comments

softest-engineer.bsky.social•19 days ago

Yes! We’ve been working on this in #LeetcodeLunch

maiproject218.bsky.social•19 days ago

Ill make sure to join next ones with you! Have to cement it in more :)

ncoughlin.com•19 days ago

I’ve never understood why people are so stingy with useMemo. Anything that results in a non-primitive gets a memo in my book.

I just hate debugging infinite render loops. I spend way too much time doing that.

maiproject218.bsky.social•19 days ago

They are? Id love to know why others are against it if it makes time complexity run faster and less debuggging down the road

ncoughlin.com•19 days ago

Technically it has to perform some kind of calculation for each useMemo on every render which “in theory” could take longer than simply declaring a variable again. Because of that I’ve heard many describe useMemo as overkill in some situations.

maiproject218.bsky.social•19 days ago

Ah, I can see that occurring with each render. Thank you for mentioning it to me. I will have to weigh the tradeoffs before utilizing it in the function I'm using it in.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply