Readit NewsCelsius is for chemists.
Celsius works significantly better in cold climates for reasons mentioned in another comment.
For scientific work I obviously prefer kelvin.
Celsius is nearly useless.
+10°C is "it's somewhat cold, put a jacket on". +20°C is comfortable in light clothing. +30°C is pretty hot. +40°C is really hot, put as little clothing as society permits and stay out of direct sun.
Same with negatives, but in reverse.
Boiling water is +100°C, melting ice is very close to 0°C. I used that multiple times to adjust digital thermometers without having to look up anything.
It's the most comfortable system I can imagine. I tried living with Fahrenheit for a month just for fun, and it was absolutely not intuitive.
- Both in same password manager is obviously storing together.
- Both on same phone, but different apps. There are the subvariants of: password manager and dedicated OTP app or two different password managers. Also there is the consideration where the apps really store the secret data, e.g. system provided vault
- OTP on a separate device
I think the middle option has too many ifs and buts and you could argue that as long as its the same device it's not really separate.
So dedicated OTP token. What should I use?
Cheap mobile phone? Does it need a SIM? Are there dedicated devices? Can they store multiple keys?
https://www.token2.com/shop/category/classic-tokens
https://www.token2.com/shop/category/c301-tokens
https://www.token2.com/shop/category/multi-profile-programma...
Other vendors probably have something like that, I link to what I've personally used.
The problem is one of degrees - Anyone you notice on a big site is likely posting very often - "Terminally online" is the word. The more niche you go, they are alternatively deeper into their own fantasy worlds. I haven't figured out how to arrange coincidence; Repeated coincidental meetings have long been studied to be the basis of friendship, and intentionally going to "meetups" where the attendance is common but not fixed is the best way to foster that.
Online matchmaking has been the biggest problem here - You are guaranteed a game, but you'll never run into the same people twice. Once upon a time you had localish communities form around servers that were low-ping to them, which really worked well - You were likely to run into the same people, and they were likely to be nearby but not so close that you'd have run into them anyway.
https://direct.mit.edu/rest/article-abstract/99/2/229/58403/...
We have a build for a giant xyz customer system. Every part of the codebase is modern; it has thousands of JUnit5 test cases, 26+ modules. We've set the build up "correctly": following Maven best practices and it turns out, when you follow them, things are really quick with builds just under a few minutes.
Eclipse does an amazing just handling a project this size. It also is able to do things VsCode simply cannot do. We had a enum we needed to move from a submodule to a a global one. Eclipse found all of the references, including ones in our documentation, strings, test cases, and even prop files for runtime config, and refactored the whole thing in a few clicks. We've had the same experience with IntelliJ actually too, where the tools are even more refined.
Eclipse/IntelliJ are on a different plane. VsCode does have it's merits, but it's not really a full blown IDE.
The level of code refactoring tools available in IDEA dwarf anything vscode has been able to come up with, and I don't see that changing. And it's not just for Java (although it gets the best tooling), they're the best for every language that has any popularity at all. Including TypeScript, where IDEA has a significantly better performing lsp features than vscode.
For example, it automatically finds copypasted code (including cases where variable names and code structure might differ) and can automatically extract a single implementation and generalize it for you with a single key press. If you have multiple classes with similar interfaces, it can extract the common bits into an interface and update the classes to become its implementations. It can shuffle types and methods around for you, automatically updating references (which you've mentioned). Autocompletion for absolutely everything, including difficult cases like e.g. SQL inside a Rust snippet inside Markdown. And much more.
40 F is a good time for getting winter tires on.
As someone who lives in a humid, wet area that goes from -40 at night in winter to 100+ F in summer, I also vastly prefer Fahrenheit.
The difference between 60, 70, 80 and 90 is pretty profound with humidity, and the same is true in winter. I don't think I've ever set a thermometer to freezing or boiling, ever. All of my kitchen appliances have numbers representing their power draw.
I too live in a region with 80 (Celsius) degree yearly variation (sometimes more; the maximum yearly difference I've lived through is about 90 degrees IIRC: -45 in January to +43 in July), and Fahrenheit makes absolutely no sense to me in this climate.