I can only speak for myself, but I'm just glad you're still a member of these communities. Take care of yourself, and I look forward to many more years of learning from your code!
Couldn’t agree more — Much like running my own DNS or email server, I don’t think I’ll ever go back to running my own website directly on the internet. It’s just not worth the hassle. For stuff only I use, it sits behind my VPN. For anything that _must_ be public, it’s going behind a WAF someone else can run.
I will given Berlin credit here — after checking in to our accommodations (took a taxi from the airport), I poked a ticket machine, quickly saw the Union Jack flag and got the machine into English. Couple minutes later we had our 1 week passes in hand. In general I found the system very approachable, using google maps for route planning.
I mean yes — that’s the point. If untrusted parties have access to your keys, it’s already game over. You’ve lost. Disabling them is the nicest thing an attacker can do for you.
Canadian but also lived in the US. Have not lived in the EU.
For Canada, while geographically large population wise it’s very small compared to the US. The big Canadian banks are targeting a similar sized demographic to California.
I’m less familiar with Europe, but I’m guessing most nations still have prominent national retail banks, with some having an EU wide market? Those national retail banks would effectively be regional in the US.
In Canada, electric block heaters for the engine are fairly common as well: https://en.m.wikipedia.org/wiki/Block_heater . Similar concept to fire under the engine, but a bit more modern
This isn’t entirely true fwiw. That assumes a constant load on the systems. If you start running into a capacity crunch on a given system, your best case is scale horizontally or vertically using established procedures. But if you hit a limit there (vertical scaling limit, architectural limit) and actually need to refactor? Good luck!