When I worked in tech in Germany, we had no union and my WFH contract explicitly said I could be reassigned to any office at any time.
A friend in another industry had this happen: management forced everyone out of Berlin (or you could take a package). He ended up having to move for five days per week.
I'm a Software Architect and Principal / Staff / Founding Engineer, looking for my next big career move.
I want to make the world better by solving real problems with software.
Looking for an ambitious company with far-reaching impact and talented, professional staff. My "happy place" is closer to the customer than to the metal, while still designing and building server software.
The CDC doesn’t record medical malpractice as a category for cause of death or injury. It’s grouped under “accidents” in their statistics (their official 3rd ranked category).
> The CDC’s published mortality statistics, however, count only the “underlying cause of death,” defined as the condition that led a person to seek treatment.
Because of this political choice the information comes from 3rd parties digging into the accidents category.
I had private health insurance in Germany. It was quite expensive and had a very high deductible — so pretty bad incentives around routine health care, I never made a claim in 13 years.
The upside was that if you needed, say, a brain transplant for ten million Euros, as long as it was medically necessary they would pay for it.
Now I have a policy elsewhere that is cheaper, still covers me when I go to Europe, and has a much better copay structure while being 100% private. Downside is I can’t afford that brain transplant, but I’ll probably be OK for everything else.
But if a procedure is medically necessary in Germany, public insurance pays for it too (and if they deny, you can, often successfully, appeal or sue them). The biggest difference is that you’ll get an appointment much faster due to the quota system for public insurance patients, and that private insurance can cover more things that aren’t strictly necessary.
The crazy thing is that I originally signed up for private because it was cheaper than public… at the beginning anyway. I much prefer the Austrian model, in which — I believe anyway — everyone has to pay for public, but then you can get extra private on top if you like.
I was an employee so this didn’t apply to me, but for my freelancer friends it seemed very unfair that they had to use private.
>But if a procedure is medically necessary in Germany, public insurance pays for it too (and if they deny, you can, often successfully, appeal or sue them
When you're very sick you hardly have time, money and energy do deal with a lawsuits so that you can get the care you desperately need. By the time you win your lawsuit you could be dead or your condition worse from the stress.
I’m a standard-issue stress eater. I also like to work out.
When I’m really feeling the stress, even though I will tell myself at that time to just hang on and hit the gym later, the food is that much more of an instant fix that it wins out more often than not.
I’m sure that’s not just the actual food itself, but also the easy availability of it, and probably subliminal cultural factors such as advertising. But partly, yeah, it’s that my ancestors evolved to love eating when they had food, and their gift to me is that same desire in a world of endless plenty.
I like Hesse and I like Steppenwolf even though neither is my favorite -- but there is a fragment in Steppenwolf that I will never forget, that I have used often, and that anchors the love side of my love-hate relationship with the German language:
"...um im Gasthaus [...] das zu trinken, was trinkende Männer nach einer alten Konvention »ein Gläschen Wein« nennen."
English: in order to drink in the pub that which drinking men, according to an old convention, call "a little glass of wine."
A lot (all?) of the points I make aren't unique to rust, or even invented in rust. Many have even better implementations in other languages. Go also invented the "fmt", with one opinionated code style "enforced" by default - bikeshedding be gone!
My point was that it's the combination of all of these points. AFAIK, go ticks many of these boxes too. But for me golang falls short with mutability, and with the type system (though that one's catching up really fast). It's the "package-deal" that I like about rust.
I much prefer rust to go for many reasons, but IME go gets this part much better. Darwin / Linux cross compilation, armv7, FreeBSD, oh sorry you don't have a linker for that toolchain, wait where are those OpenSSL headers... lots of cross-compilation targets I've done in minutes with go that scp and run right away that end up being days / weeks of adventures to cross compile in rust, in spite of me knowing rust much better than go at this point.
I have had the luxury to work in projects that don't have to target many platforms, but rather "one": a server. Which then is often a simple linux variant so setting up a CI or even the local build to target that "one" is relatively simple.
But wasn't Go a lot more limited in the amount of targets it can build for than rust?
Yes and no -- obviously I can build for no_std targets like esp32 and atmega128p in rust but not go (haven't tried tinygo), but the proportion of targets that successfully built and ran IRL has been higher for me with go. On rust, the dynamic linking of libc (by default) and failure to include a linker with the toolchain have repeatedly been stumbling blocks, go "just works."
A friend in another industry had this happen: management forced everyone out of Berlin (or you could take a package). He ended up having to move for five days per week.