I think there are no safe harbor investments at this time. Even gold is unpredictable.

Personally I went 80% world excl US and 20% equal weight S&P500 to hedge against what I think is an AI bubble. But if the market decides to adjust Nvidia's valuation 20% downward next week, I expect there to be ripple effects throughout the economy.

(Like the .com bubble, I think the tech is genuinely transformative and here to stay, but the valuations are just ridiculous.)

The notation is supposed to mean: you have a matrix Q, and also a shared K=V matrix.

I agree with GP that it's super confusing to us the minus sign as a delimiter between formulas. The tuple notation suggested elsewhere would be way clearer.

IMO the easiest way to open the straight is for the US to back down. "The EU helping the US" doesn't sound like a great way to achieve that.

I don't want the EU to join a protracted Iran war.

I don't even see how this is a controversial opinion to hold. Israel blatantly roped the US into an unwinnable political conflict that can only escalate. Any rational politician will see a quicksand pit out of this scenario, and many military analysts arrived at the same conclusion in the 1990s.

Europe cannot contribute relevant naval power to reeopen the strait. They cannot significantly turn the tides in a ground invasion, nor do they have the impetus to. The only thing they can do is legitimize Israel's war, and why would they do that? It's not like America or Israel are any closer to achieving their key objectives, Europe wouldn't even get a tour-de-force out of it. This is purely CENTCOM's fuckup, NATO has nothing to do with it.

Nope, no one else should definitely not get involved. The moment the EU or anyone else joins, Trump will pull out and leave it for others to clean up.

I agree with the sentiment, but this is not something I can send my colleagues.

You can be annoyed and right, and still avoid being crass.

Perhaps this falls into "how to have hard conversations" bucket?

If I told my coworker that his or her "brain is a gizmo" and to "not reproduce" I would expect to be frog marched out the door a few minutes later.

"Your brain is a gizmo" doesn't sound very harsh to me, but "please don't reproduce" would be a problem in any reasonable workplace.

Established accounts are worth money, often for scamming/propaganda.

Not too dissimilar to people bot-leveling in MMOs to the sell the accounts.

I'm afraid you're mistaken. He hired a cartographer to iterate over the design, but from the images, he likely used that feedback to create a map style.

For example https://wiki.openstreetmap.org/wiki/Map_style

However, you're also kind of correct in that the rendered tiles are typically cached server-side (presumably also for Apple Maps).

Genuinely curious: what would you have had him do instead?

Everyone is writing. Nobody is reading.

In my over a decade of experience as a software engineer, writing code was always a smaller fraction of my time compared to reading code, debating code with colleagues, and wrangling ops. Optimizing for velocity of writing code will inevity lead to spaghetti at best and vaporware at worst.

There is also discussion, ping pong with the agent, exploring parallel paths, quickly experimenting, analyzing code, researching things. A code agent can do more than "write me as much code as possible, go!".

That's how I use agents, but I see less experienced engineers brag about how much code they pump out and it makes me cringe

I feel like this take misses what LLMs actually bring to the table to a senior developer.

Sure writing code was not the majority of my workday since I moved up in responsibility chain - but that's because I don't get enough uninterrupted time to do the actual coding from all the meetings, syncs, planning, production investigations, mentoring, team activities.

Now that I can delegate code writing to LLM instead of mid/junior devs the dynamics of those tasks change dramatically. The overhead of managing more junior devs is completely gone and no need to have soft skills with an LLM. And communication/iteration speed with LLM is not comparable.

Not to mention I don't need soo much time to get back "into the zone" - LLM can keep working through my meeting - when I'm back it's already working on something and I can quickly get back into the gist of it - much faster than before when I had to take a break and lost all context of what I was doing an hour later. LLM has all that context + more progress right there.

After soo many years of dev I have a pretty good idea of what I want the code to look like - no need to debate the overzealous mid dev about his over abstracted system that's going to haunt me in a production outage next month when we both forgot what he put in - I simply get to say "this is shit rewrite it how I requested". No need to "talk about latest lib that's all the rage on the YouTube blogs etc."

Sure sometimes I realize that doing stuff without LLM would have taken less time - but when I consider how many interruptions I have between my coding sessions - LLMs are empowering precisely because I get to dedicate so little time to my code.

Also less teammates means less communication overhead.

The LLM's do quite a lot of reading. The question is what to feed them. (What counts as good context?)

I do wonder if it's fair to expect users to absorb cache miss costs when using Claude Code given how untransparent these are.

Where I live, your employer basically has to give you notice (weeks to months, depending where you live). It's common for that notice period to turn into "garden leave" though, i.e. get paid but don't show up.

Mass layoffs, or RIFs, operate under slightly different rules, but I still saw a stark difference between US and EU employees when I went through one at a different corp.

US accounts were deactivated same day. EU employees were given until end of week to look over the proposed terms etc.