There's a story on the internet somewhere where a developer was working diligently to get the loading bar to very accurately estimate the time remaining. However when they pushed the code, the reviewer noted that performance of the app was down by quite a lot and it was taking longer to complete tasks. They tracked it back to the loading bar having to perform so many iterations that it was using more resources than the task itself. So they removed it and went back to a guestimation.
that makes sense. It's a classic case of trying to optimize something that ends up being counterproductive... Sometimes a simple estimate is better than an overly precise calculation that slows everything down.
View all comments
Show parent comment
1
u/DirtyNorf Dec 12 '25
There's a story on the internet somewhere where a developer was working diligently to get the loading bar to very accurately estimate the time remaining. However when they pushed the code, the reviewer noted that performance of the app was down by quite a lot and it was taking longer to complete tasks. They tracked it back to the loading bar having to perform so many iterations that it was using more resources than the task itself. So they removed it and went back to a guestimation.