I feel like he jumped into “hard” optimisation too fast.
I would say when you find code running slow, first you do:
only do nessesarry work,
if we only need to look up a persons name we do not need to load all and everything and their image for that person from a DB, File or alike (fewer calls)
dont do the same work twice,
if you already calculated something you might not need to calculate it twice (example: caching)
then if perfromance is still an issue, do what he suggests in the article :)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
deleted by creator
All jokes aside, I like the way this article breaks down types of optimizations. Especially the forth, as that tends to be the answer on occasion.
I feel like he jumped into “hard” optimisation too fast.
I would say when you find code running slow, first you do:
only do nessesarry work, if we only need to look up a persons name we do not need to load all and everything and their image for that person from a DB, File or alike (fewer calls)
dont do the same work twice, if you already calculated something you might not need to calculate it twice (example: caching)
then if perfromance is still an issue, do what he suggests in the article :)