Unrealized gains can be taxed - for example, Ireland has a Deemed Disposal tax on ETF investments, where after 8 years, any gains are considered to have been realized and tax is due (even if no sale has taken place)
Deemed disposal subject ETFs can be taxed under an eight year exit tax scheme, but this can be avoided by simply investing in US domiciled ETFs or individual stocks.
Definitely not new - as someone who was diagnosed with Haemochromatosis in 2017 - I was first prescribed phlebotomies until my general iron levels reached a level that my consultant was happy with.
Once I hit that level, I'm able to donate blood about twice a year (once every six months) to maintain (that, and a slightly changed diet to avoid high iron food)
The first line (or atleast, the first 80 characters) should be a quick summary - so you can quickly browse via git blame.
But the actual commit message should consist of History/Motivation/Context - so that someone who's going through the blame can understand why a certain change was made, and what the context was.
If I want history, motivation and context to actually be read at some point I put it in tests, code comments and README/docs.
If I want my history, motivation and context to be ephemeral I put it in a commit message.
It still perplexes me why people obsess over commit messages while the places where people are actually looking when they have these questions are neglected.
I don't particularly want a commit log at the top of every function, TBH. If I'm looking for the history and context of a change, I want to look at the commit log. If I want a description of the current version, I look in the docs (and yeah, sometime I can only piece together why something is the way it is now by looking through how it's changed. But documenting each change has a much better chance of addressing questions like "why did it work and now it doesn't" then trying to get the docs perfect will.)
{Tests, Code Comments, Documentation} are 3 distinct places to trawl through when quickly going through git blame.
The commit message is one place - and gives the author an opportunity to speak directly with a future developer over the place-in-time-context that this change was made.
Git blame is something you use to ask "what the fuck"? Hence why it's got the tongue in cheek moniker "git blame".
If devs are constantly asking "what the fuck?" all over the code base then that's usually coz tests, code comments, docs and code quality were all badly neglected.
Better commit messages are a band aid over that gaping wound.
You're focusing a bit much on the Developers bit.
It's not just Developers who are working through the code-base.
As a lame example - Incident Response/SRE will also be trying to get their heads around changes being made - especially if they're responding to an outage, and trying to figure out what change broke production - and why it was made.
Not everyone will know every bit of the project as intimately as the Dev team - and having a good commit message will help any unfamiliar response team mitigate, or escalate accordingly.
Behaviour by the rest of society is influenced largely by public policy.
In Ireland, investing in Housing/Land is largely one of the best investment assets you can own due to the lack of Capital Gains or Deemed Disposal rules.
Helmets prevent a particular type of injury - traumatic brain injury
This is true for all types of transportation including driving.
Traumatic brain injury is a common outcome of an automobile collisions - yet we don't see people with the same concern for introducing mandatory helmets in day-to-day driving.
A few of the offices even have a pool (Google Dublin, and soon Google London)
Because the buildings are usually located in very central city locations
- I've often used the offices as a way to kill time til' check-in opens for hotels after a long-haul flight (grab food, caffeinate, have a shower, etc)
Recently I took a night train between Stockholm and Copenhagen.
Showered in the Stockholm office, walked 5 minutes to the train station, slept, woke up in Copenhagen, grabbed a hearty breakfast in the CPH office.
It's a little perk that is honestly vastly underestimated
On the topic of the perk of just showing up to an office and being able to get in, I completely agree that it's underestimated. I visited the Zurich office once and my flight got in at some terrible hour after a bad Frankfurt connection (aren't they all though?). I couldn't get in to my corp housing, but I just rolled up to the office with my suitcase and walked around giving myself the tour while the buildings were ghost towns. I think I dozed off in some room that had an aquarium.
Likewise, one time I was on vacation in Hong Kong and just waltzed into the office and hung around for a little while. I actually ran into a friend of mine in the office who I had no idea lived in Hong Kong or worked for Google at the time.
YouTube's San Bruno office (well, the Gap building at 901 Cherry) has a gym and pool. It's also bright, airy, and did I mention bright? So much natural lighting, it would be a shame if you had a super glossy monitor and no way to block glare 4 hours out of the day.
I got a tour one time of some of the less-visible infrastructure of the building. There is a huge concrete slab under the building that acts as a heat bank, and somewhere there are windcatchers (I don't see them in aerial photographs) which funnel air over the concrete before it goes into the interior. This keeps the inside cool in hot weather and warm in cool weather, without an active air conditioning system.
It's also nestled in the 280/380 interchange, so my commute very often took me up and back down on 280, which is probably my favorite stretch of road in the world. I grew up in the south bay, a stone's throw from 280, and driving up and down 280 has always been relaxing for me, even when there's (somehow) traffic.
In retrospect, I didn't fully appreciate that office. Thanks for the 5-minute reminisce.
That's interesting to hear that it is so relaxed in Europe. I work in EU at a multinational with offices all around the world, and within Europe, we are not legally allowed to enter the offices in other countries. The reason is simply that if there is a labor/work inspection (sorry, don't know the exact English expression) they can get a fine if I do not have a work order for a project abroad.
This is true in the US, too, but selectively and only really enforced in a meaningful way by a few states (including California). If you spend 30+ days in California for work reasons (visiting a employer's office would count, even if you're not on the clock when you do it) it triggers state income tax requirements. No fine, but equivalently unpleasant.
