There is an art (and a science) to numerical precision that seems lost in software, writing and conversation. The trick to appropriate precision is understanding accuracy. This all falls under the banner of numeracy.
For example, I just received a confirmation of a cinema booking that gave the time of the film in HH:MM:SS format. The site lists programme times in HH:MM. They normally start trailers within a few minutes of the advertised time. To list seconds is an innumerate and false promise.
I sometimes receive notifications that I can expect a delivery in a 2-hour window such as "between 12:07 and 14:07".
To quote to the minute shows a failure of understanding of what an approximate range is, as well traffic and logistics.
It's a 2-hour window of imprecision. Quoting to the minute shows a deep lack of understanding. Quoting to 5-minute intervals is just about acceptable. To 10- or 15-minute is more appropriate significance. But honestly, in this case, to the hour is just fine.
In such cases, it makes the company and the software authors look incompetent and clueless about their own domain, whereas they should present the exact opposite.
This doesn't mean that your plan or your calculations don't contain such precision, but there is an art to presentation logic and UX that has been developed over many decades β as well as experimental science and metrology over centuries β that often seems thrown out the window when it comes to presenting something in a window.
I disagree, that it's an art, that these developers fail in. It's the essence of their craft: communication. Code is communication, nothing more, nothing less. If you fail at communication, you fail at programming.
Kevlin Henney
ππ±π»π²πΌπ½πΈπ― ππΈπ·πͺπ½