An expanded view of that is that there's usually a "current" meta strategy that people tend to adhere to, kind of like a convention. And if you stray from that, you lose, even if your strategy would succeed in a vacuum.

For example, if the current meta is for employers to mainly use referrals/networking to hire, it would be a bad strategy to apply to postings.

Not to mention, that would break fungibility.

Can you provide a source?

> I keep designing physical parts for our robots. Motor mounts, sensor brackets, wheel hubs. Every time, the workflow is the same: open a GUI CAD program, click around for an hour, export an STL, realize the bolt pattern is 2mm off, repeat.

This doesn't make sense. When you realize the bolt pattern is 2mm off, you just edit that dimension and let the CAD program recalculate. You don't need to click around for an hour again. That's the beauty of contstraint-based parametric modeling as opposed to, say, modeling in Blender.

The author's program is akin to writing vim to replace Publisher. They're solving entirely different problems. Not to mention, this code-as-model paradigm already exists: OpenSCAD

Sure, there are plenty of people who get their kicks from record stores and soundcloud, but to properly make it, you need to be where the ears are.

For example, as a prospective employee, if I knew that I was the only qualified candidate the employer had interviewed, and they really needed someone within a week, I'd know that I can ask for more salary. If I instead take the middle of the salary range, just because it's maximally acceptable to both parties, I'd be missing out

- You have a strong unlock password that you don't use anywhere else

- You have a second factor set up for unlocking the vault (TPM in the device you're using, Yubikey, TOTP, etc.)

- The service you're logging into has good account recovery hygeine

The benefit, assuming those things, is that the passkey is phishing-resistant and social-engineering-resistant. If a user gets an email saying "omg, someone tried to transfer your paypal, click this link to log in", then when they try to log in with the passkey, the site the attacker is using won't be able to use the passkey (because the passkey is associated with a particular domain). Even if the user wanted to bypass this, there's specifically no way for them to extract the contents of the passkey.

That is very different from a user having their password stored in their vault. They could easily forget to check the domain, or get tricked by a very similar looking one, and copy/paste their password into the attacker's form.

I know this is just a start (and just enough to make the ROI worth it, probably), but it sounds particularly dystopian / late stage capitalism