184
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Jun 2025
184 points (98.4% liked)
Programming
20767 readers
149 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 2 years ago
MODERATORS
Nah, I was excited to read about the algorithmic change, but it turned out to be an obvious change. I would replace nested loops with a map too. The result is impressive, though.
Marketing departments love to make a huge deal out of this kind of thing, because they only see the big number improvement and don't really understand that this was just some dev's Wednesday afternoon.
Well it's a 70 times improvement so the developer gets a 70 times bonus. Or at least all the money that would be wasted without this fix.
Or is the world unfair and are developers nowadays just cogs in a capitalistic machine?
And they are right to do so. In the grand scheme of things, it doesn't really matter how much time you spend on a problem. It's the result that matters. I remember a meme where a dev would place a "wait" function in a new feature. Than remove the wait call and call it a free update and get lots of praise from the customer.
https://thedailywtf.com/articles/The-Speedup-Loop
I mean, it’s still really impressive upgrade even if technically it was a simple change, they are right to make a fuss about the change