This is how stuttering works. De-sync in the brain between when expecting to hear your own speech. Or at least one of the root causes of the symptom of stuttering. I used to stutter.

The rocks never formed. Tectonics slowed for a bit.

Preliminary study showed that vaccine + covid results in a much higher levels of antibodies and memory cells. Said that it is indicative of life time immunity. Of course more research is required, not sure how it applies to delta, and mutations can happen.

I'm not sure if newer data is out, but some official study showed that only 1 out of 1000 cases were from touch. And gave a recommendation to not worry about transmission via touch. But still sanitize your hands as that is still general best practice.

Anecdotally, our company had several remote offices that were closed permanently, and everyone at those offices kept their exact pay, made fully remote, given and extra $50/m for internet bill and some basic allowance to setup their home office. We lost about half of the software engineers saying "they don't want to work from home".

I love working from home. I know many who do. I also know many who loath it. "I want to see people again". I have no anecdotal intuition about how many who do and don't. I just know there is a sizable mix of both. Work is talking about making it entirely optional, allowing for hybrid.

I haven't seen glibc in the news almost ever. Seeing how widely it's used speaks for its relative quality. But so many people use "people make mistakes" as an excuse for shit design and code all the time. I recently inherited a project that was "done". Just needed final QA and deployment. This project was code reviewed and tested. I read through the code and found swaths of defects. I've have yet to run it and I've changed out hundreds of lines.

This is not a one time deal. This happens all the time. The really annoying part is every so often I get push back where the coder doesn't believe there is a bug even though I am showing them the code. Then I have to get all hypothetical on them. Ask them to explain what will happen if I supply such and such of a value. "Ohh, why would anyone do that, that's against the business requirements?" "Have you even looked at the data, these values actually exist because of other people not validating the same way you aren't"

Why does something go wrong? Because it can. Design your system so it can't instead of wishing on a star.

Highly regulated. My wife works at a bank and asked about when they're going to support webauthn on their web access. She was told the software they use is about 15 years old, getting new software will take years to get setup and certified. They're biding their time to see where tech goes because whatever they upgrade to, they're stuck with for 15-20 years.

From the sounds of it, they're using one-off bespoke systems. Every upgrade requires reverse engineering of the old system in order to transition to the new one, and lots of boot-strapping issues trying to cut over.

I would be curious about that. From everything I've read, NFC only has meter distance between two powered devices. If one of the devices is passively powered by wireless, then the distance is more like mm to cm. One example of a passively powered NFC device is my yubikey. I have to touch it against the phone, flat. If I hold it with the very tips of my fingers so it's not quite in contact with the phone, it can take several seconds before it even attempts to auth, and many times it still fails to finish the auth.

USA average is 11KWH/day/house. Apartments are more like 4KWH/day. Focusing on just normal home with attached garage, 7KWH. These are averages. I know people with high efficiency homes that can run their AC down to 65f at night, turn off their AC when they get up in the morning, and still be below 75f by bed time when they turn it back on. And that's with it being in the 90s outside. Then I have my duplex where the AC has to run 24/7 just to keep it below 75f when it's 80f out.

And the velocity of the wind is a somewhat linear increase as they get taller. And energy increases with the cube of velocity. Energy extraction is closer to the cube than square.

People have a +-50% difference in gut absorbed calories. This means that if you take two reasonable outliers, you can have one person who absorbs 200% more calories from the same meal. That's only one factor. Then you need to factor in metabolism. And the body is designed to protect itself from too much fat loss. It is very normal that if a heavily overweight person tries to lose weight, their body thinks it's starving, lowers the metabolism, and starts converting more incoming calories into fat to replenish the lost reserves.

This barrier to entry can make losing weight very difficult as your body literally thinks it's starving, makes you feel lethargic, and can interfere with your life until it eventually re-normalizes some many months later.

I think it's NIST, or one of those, that requires all forms of authentication to be mutable and revocable. This makes biometrics and invalid form of authentication.

Password managers work because people are incapable of doing what you suggest. Why not just expect everyone to memorize a unique 20char random password for every site? You ask for the impossible. For every person you can find an example of your convoluted scheme, there are 100 million other people who would never do that.

Fusion testing has resulted in massive lasers that have reduced output beyond certain levels because some percentage of the additional photons were converting into matter instead of more luminosity. The only thing new is the difficult 2 photon issue.

I only recently got involved with our companies hiring process and we have 2 interviews. Meet with our team lead. If they determine the candidate is worth our team's time, then we have a full team interview that is broken up into chunks so the whole team isn't in the same meeting at the same time. It's all remote and we're very flexible with time.