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

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).

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.

Foundational:

- Pretraining - Mid/post-training (SFT) - RLHF or alignment post-training (RL)

And sometimes...

- Some more customer-specific fine-tuning.

Note that any supervised fine-tuning following the Pretraining stage is just swapping the dataset and maybe tweaking some of the optimiser settings. Presumably they're talking about this kind of pre-RL fine-tuning instead of post-RL fine-tuning, and not about swapping out the Pretraining stage entirely.

Instead of saying "are you sure?" or "shouldn't we do X instead?" you could say "give me the benefits and drawbacks of this compared to X".

Also, when you yourself are sure, give clear stear. "This overcomplicates A, let's do B instead."

There is no incentive for adding false positives to lists of malicious websites.

[0] e.g. something like the below which I expect to use maybe a dozen times total.

Main routine: In folder X are a bunch of ROM files (iso, bin, etc) and a JSON file with game metadata for each. Look for missing entries, and call [subroutine] once per file (can be called in parallel). When done, summarise the results (successes/failures) based on the now updated metadata.

Subroutine: (...) update XYZ, use metacritic to find metadata, fall back to Google.