That’s funny because when I work with Fahrenheit I just work with 5°F ranges to compensate for the approximate mental math required. Eg very quick mentally, 100°F = 37.778 °C (thanks autocorrect) = (100-32)/2 = 34.
But if it was closer to freezing say 42°F =5.556 °C (again) so 5°C. So arbitrarily we could say 57°F was 12°C =53.6 °F actually.
But a true Canuck knows knowing the temp is barely half the battle, what’s the wind speed and humidity? 29°C can be a lovely day if it’s dry or completely unbearable if it’s humid.
We hardly ever use decimals for weather-related measurements, the other factors above being more relevant.
Contrast that with measurements where I would say if you need to know a precise one you should be using decimal; ie what do you do if it doesn’t precisely third or fourth? If you’re talking about tool sizes then any system works as long as your froodle matches the grommlet.
I personally find the math just as easy to do accurately. For example, 87F -32/1.8 = 55/1.8 =~30.5C. Compare that to your approximate method, which would give 28.5C, which is just wrong
(Maybe I just got really good at this when working a public facing job with a lot of American tourists - they would ask what our celsius temperatures were "in real units", so I got quite comfortable converting the air and water temps. Fahrenheit never once became intuitive to me, though.)
For C to F you can often simplify the mental math by doing the multiply by doubling then taking off 10%.
E.g., to convert 31℃ to ℉: 31 x 2 = 62. Subtract 6.2 = 55.8. Add 32 = 87.8℉.
If you want to round the result to the nearest integer the subtract 10% step is a convenient place: 31 x 2 = 62. Subtract 6 (rounded 6.2) = 56. Add 32 = 88℉.
I had a longer reply but turfed it, but the global menu is based around muscle memory for eye and mouse locations. My personal experience sounds nothing like yours so I suspect we navigate very differently such that it impacts you far more than me.
I’m a heavy keyboard user so rotating apps and windows in apps means I always know where I am and don’t even notice the costs you’re talking about.
It’s probably worth posting [1] which shows many cities around the world.
Also there’s an aging HomeAssistant add-on [2] that lets you visualize stations and stats. But since HA now insists the addon is separate from an API and there’s no separate API (really, it’s trivial) things like electric bike or trailer counts are not exposed.
In GitHub we use an OIDC token to access some AWS resources. Locally I need to populate tokens etc and so I have an `if: ${{ACT}}` and a not condition to populate it.
It’s even worse than that, it’s 20GB compressed and 60GB uncompressed. Regardless, if your VM runs out of disk space there’s no meaningful error (well 12 months ago) except a failure to start. (Possibly colima-specific I dunno I uninstalled docker-docker)
I do find that some things just work locally and fail in real actions and vice versa. For the most part it’s made it easier to move the bar forward though.
But if it was closer to freezing say 42°F =5.556 °C (again) so 5°C. So arbitrarily we could say 57°F was 12°C =53.6 °F actually.
But a true Canuck knows knowing the temp is barely half the battle, what’s the wind speed and humidity? 29°C can be a lovely day if it’s dry or completely unbearable if it’s humid.
We hardly ever use decimals for weather-related measurements, the other factors above being more relevant.
Contrast that with measurements where I would say if you need to know a precise one you should be using decimal; ie what do you do if it doesn’t precisely third or fourth? If you’re talking about tool sizes then any system works as long as your froodle matches the grommlet.