this post was submitted on 16 Jul 2024
507 points (97.7% liked)
Programmer Humor
19564 readers
557 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Somebody convince me I'm wrong.
There is no reason to display "100%" in your UI for more than a single second. Either show 99% and then finish, or show 100% only when you are ACTUALLY done and only show it for a little.
If you're still doing ANYTHING AT ALL don't say you're 100% complete. How is it still like this
I imagine it started with some sub-installations actually giving approximations that were acceptable and summed up, but then some finalizing was not taken into account or something needed to be added after the other processes are finished, and the deadline was close. That last part builds up over time with other quick additions and some annoying stuff that is actually quite performance heavy and not easy to incorporate through the whole installation. "Let's do it at the end as well."
No time / budget to change the 100% to 99% as they have to adjust calculations based on the processes that actually do a good job. Although a display change could fake it, priorities are elsewhere.