They're from levels.fyi, and if you look at Switzerland, something like 20% of all salaries are from Google employees. 100-110k is probably a better number.
I kinda disagree with other posters, even after CoL adjustments you're way ahead in Switzerland, especially given the usually low taxes. RE is totally unaffordable though, the rest is fine.
Something that has always been really appreciated, and can be an easy "first commit": update/complete the docs. There's always a missing step, something unclear, an outdated link, and undocumented "whys", something to automate, ...
When you've just joined from outside, you're in a unique position in that you haven't internalised yet all the little idiosyncrasies. Best to take note of them, understand the context, and maybe help change them.
I think this works well with at least somewhat interested students (like in university), but I'm not so sure before.
My experience when I was younger is that a significant proportion of students don't do anything outside of school. So you're trading not doing the homework with not reading the material. And then you'll essentially have to repeat the material during class hours, unless you're willing to leave half the class totally clueless. At least with the homework at home, the ones not doing anything are only penalising themselves.
I totally agree though that homework at home is dying. It already wasn't great before for a variety of reasons, and now it's basically totally useless.
And even when they're forcibly removed (e.g. via a vote of no-confidence), they often keep on doing the job until a replacement is found, albeit with limited scope/powers. See France for instance recently.
Switzerland has them for supplementary health insurances.
In a nutshell, Switzerland has two types of health insurances. The basic one, which is mandatory, and whose coverage and price is set by the government. It covers more or less everything that endangers your health. Pretty close to ACA in the US if I'm not mistaken, but a lot more regulated.
And then you can add supplementary insurances, for stuff like dental, private rooms in hospitals, experimental treatments, ... It's common to be denied coverage there, especially as you get older.
I think it does reduce readability in some scenarios.
For instance:
const auto& processes =
getCurrentlyRunningProcesses();
for (const auto& process: processes) {
// Ok, what do I do with process now? Is it a pair from a map? A struct from a vector?
// If it's a pair from a map, is the key the pid, a unique id, something else?
}
std::unordered_map<Pid, ProcessData> is more readable than auto here IMO: you don't need to open the definition (or hope your IDE correctly display the type).
Free international messages/calls as well. That's how most of my friends and I started using it: studying abroad is pretty common in Europe with Erasmus, or even simply vacationing.
Before that, we were using Skype, but I remember WhatsApp being so much more convenient/better, especially on mobile.
If it would have been very costly to send an SMS/call a different US state, I bet WhatsApp would have taken in the US.
I have to admit I have a hard time relating your comment to my experience.
I remember a case where we were using a library throwing exceptions when it could not parse some string. I think we were parsing IP addresses, or something like this. There was a case where this was called in a hot loop (like thousands of IP addresses in a roe) and for whatever reason in some cases most of them were invalid, thus throwing. Then simple error handling: the caller catches the exception, logs the error and checks the next one.
The program was frozen for seconds. Replacing the parser with the same logic but returning a bool instead was something like 1000x faster. That was on MacOs Clang Arm.
I don't see how a few extra ifs (though none were required in this case) would change anything.
Generally I'm not a fan of exceptions, you never what something is going to throw. The majority of the crashes we see in production are unhandled exceptions. Turned out the documentation did not mention that this function could also throw std exceptions on top of the lib ones in this specific case.
You can always find a case where you are stressing the very thing that people are using in a micro-benchmark; like, no one is claiming that table unwinding is the correct choice for every single function!
But, the other extreme you get is saying all error handling should be done with checks and branches, and the idea is that this slows down the code which isn't throwing lots of exceptions so much that, for average workloads, it is the wrong tradeoff.
Ideally, you could make this decision more locally, and yet continue to use the cleaner syntax which comes from structured error handling, but I don't know of any language which implements this :/.
And, so, the best we have is to just use a language which maps exception syntax to tables as you can always -- as you did -- fix the few places it matters to use a result type by adding manual checks.
There was a parliament election, with three blocks each gaining roughly a third of the seats.
The block that won the most seats (but not enough to have a majority) immediately declared they would never compromise/ally with anyone else. Essentially, if they were called on to form a government, they were almost certainly going to be immediately censured.
So Macron, rightly or wrongly depending on who you ask, decided to not call on them since he estimated it was bound to fail and waste time. Instead, he nominated someone from a (now) minor political force because, at least in theory, they were enough people willing to negotiate with them to form a majority. Looks like it didn't work in the end and now France will be stuck because no one is willing to compromise.
