sjburt

The leap day system handles the mean, the leap seconds handle the variance around the mean. The need for leap seconds is not predictable—they zero out accumulated error.

My attitude has always been that code review is best thought of as the gate where code goes from being owned by the author to being owned by the team or project. The code I'm reviewing is not your code, it is code that is about to become our code.

Maintainability is a major factor in that, of course.

The diffraction limit (under 1.22 h* lambda/d) of a 1m optic at 250km in visible light is about 17cm. How can you achieve 10cm resolution?

At least a few years ago (~2014), the fare search was actually nearly instant, but all major airfare search sites added a delay because customers had the impression they were getting a better deal when they had to wait. It seems like the delay has been dialed back lately.

I’m not sure why people are making a big deal of it. At my gym it took maybe 3 minutes. You tie a knot and show you know how to take up slack. And it only needs to be done once.

There is a second test for lead but most people take a class and get the lead card during the class.

When you are modifying a long closure and don’t notice that you are shadowing a variable that is used later.

I know “use shorter functions” but tell that to my coworkers.

The worst part is that the sales person has to go back and pitch their team on whether it’s worth their time to get back to you.

Really curious about this:

> If you have access to a program named 'Purify' ... learn how to use it.

Anyone know what this was or use it?

“10x price hike” would have been totally clear. “Factor of 10 price hike” would probably be a formal way to say it.

How is this any different from going into a Panda Express and trying to order in Mandarin?

I think it helps that the technical concept that drove the main plot was a very real and still-present risk to public key encryption systems.