this post was submitted on 14 Jan 2024
13 points (88.2% liked)

Programming

17022 readers
235 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] pinchcramp@lemmy.dbzer0.com 6 points 8 months ago (3 children)

Am I understanding this correctly that dynamic programming == breaking a problem into smaller (reoccurring) sub-problems and using caching to improve performance?

[–] tatterdemalion@programming.dev 7 points 8 months ago* (last edited 8 months ago)

It's slightly more nuanced than that, but you've got the basic idea.

[–] MadhuGururajan@programming.dev 4 points 8 months ago

The caching is kind of mandatory as the sub-problems interact.

[–] bitcrafter@programming.dev 4 points 8 months ago

That is conceptually how dynamic programming works, but in practice the way you build the cache is from the bottom up rather than from the top down. It's a bit like how you can implement computation of the Fibonacci sequence in a top-down manner using a recursive function with caching, but it is a lot more efficient to instead build it in a bottom-up manner.