Uh, I assure you, if a fly hits something at a relative 75mph it’s not just going to be stunned.

You can kill a fly (though usually only stun) by smacking it out of the air with you hand, which has a max speed of ~22mph.

75mph is closer to a flick (though I believe a flick can go up to 100mph). A flick is enough to cause a fly to explode.

ETA: Not sure why I didn’t just say hitting a fly at 75mph with your windshield is more than enough to make it into paste.

Whoop yeah good catch but I’ll leave it.

Yes, absolutely.

“Never break main” is the same concept as “never get in a car accident.” Good in theory, but it’s no replacement for insurance.

Everyone makes mistakes. PRs help catch those mistakes. Yes, bugs will still sneak in, no one is perfect, but a proper PR process is absolutely vital no matter the team size.

Why would the answer ever be anything other than 5?

Let’s just go full boar hypothetical: Someone is trying to merge malicious code. Anything other than 5 means the malicious code gets merged.

That’s just the norm tbh. You learn new techniques, the language gets new optimizations, keywords and shortcuts. That doesn’t mean your code is unmaintainable.

It really depends on the situation. Can I write maintainable code? Yes, to the extent that the average senior dev can.

But that isn’t the same as being afforded the chance to write maintainable code. I’ve been part of teams where the timeline is so tight that technical debt is just a thing that builds up to be dealt with “later” and more stress is put on getting things done instead of keeping things maintainable.

The fact of the matter is that humans can while LLMs currently can’t.

On top of that, a human dev is going to be able to understand context a hell of a lot easier if they’ve previously worked on it, even if the code is less maintainable.

I get the sentiment, but please don’t. You’re just going to get yourself an assault charge, and the wearer will only be more emboldened.

It was released into the wild in 242H, so around a year or two ago.

M$ sudo has been around for a while as a dev setting iirc.

It’s not DNS

There’s no way it’s DNS

It was DNS

You’re a monster. And also my type of people.

I’m curious what you think tricky is?

For instance, 1Password requires your secret key for initial login/setup on a device along with the username and password. After initial login/setup the secret key is no longer required, but you still need the password to access.

I’d call that a fair trade off. Someone would need to know my password and have unfettered access to my previously set up device to login, or they would need to know the secret key.

The secret key is not stored by 1Password (the company). If you store it in 1Password and the last device is lost/broken/stolen then your account is essentially dead. You have no way to get back in.

That’s an implementation issue, not an inherent problem with passkeys.

Arguably less secure than email.

Lmao, I was going to reply seriously until I realized what com we are in. That’s some good bait.

Simplest way I can think to explain it is that it’s similar in concept to SSL. If you understand SSL you should be able to understand passkeys.

I slightly appreciate it, explicitly when it’s a service that excludes voip numbers.

What password manager doesn’t support passkeys these days?

I’m pretty sure neither is pure? I mean, you don’t have to necessarily limit steam to games. May as well try non games and see what happens.

Yeah, I’ve been guilty of coming up with “cute” solutions that are extremely optimized and concise, but you needed to take a hundred times as long to work through what was going on.

Usually I would put an explanation comment, but sometimes a less optimized solution is the better option for readability sake.