No, even if you only had one unit for a physical quantity, you would still need to specify that unit to know which physical quantity you are describing. E.g. "That object over there is 15" vs "That object over there is 15 kg".
The symbol for temperature, measured in Celsius, is "°C". It's atomic and can't be separated, since that would result in °, which represents the angle of something, not the temperature, and C, which is the symbol for Coulomb, which measures electric charge.
The source paper is available online, is published in a peer reviewed journal, and has over 600 citations. I'm inclined to believe it.
That's why these systems should never be used as the sole decision makers, but instead work as a tool to help the professionals make better decisions.
Keep the human in the loop!
As long as it's maintained. Wrong documentation can often be worse than no documentation.
Comment should describe "why?", not "how?", or "what?", and only when the "why?" is not intuitive.
The problem with comments arise when you update the code but not the comments. This leads to incorrect comments, which might do more harm than no comments at all.
E.g. Good comment: "This workaround is due to a bug in xyz"
Bad comment: "Set variable x to value y"
Note: this only concerns code comments, docstrings are still a good idea, as long as they are maintained
Damn right, you'd miss the Pan Galactic Gargle Blaster drink before the dinner. Not ok.
Not the Doppler effect, as that only applies to moving objects, but instead the inverse square law, where the energy of the sound wave decreases by the square of the distance from the origin, since it spreads in a sphere with the energy being spread across the surface of the sphere, resulting in a very quick dropoff in the loudness.
Isn't it also partly that as processing power increased, you could do more sophisticated compression/decompression in real time compared to previously, allowing these more complex compression algorithms to actually be viable?
I.e. they actually knew how to do it before, they just didn't have the power to implement it
I mean, you just have to specify the format of the url that the search engine uses, and then the browser just formats in your search string into that. This has existed for years, if not over a decade, at this point, at least on desktop.
Now I imagine them just writing an incoherent string of words. "Tomato car house fireman oven duck garden rice..."
I disagree, and would argue that both are about equally frequent. For example, my phone shows °C in the weather widget, while the weather app only uses °. That does not change the fact that the actual unit is °C, and that would not change even if the whole world switched away from °F, and your original comment about the display having °C implying that °F still exists is therefore incorrect.