officelineback

"Never attribute to malice that which can be attributed to incompetence."

I believe both services stopped exposing that information to the driver pre-pickup to lessen the problem of cherrypicking.

Can't possibly be true if you hear all the shade Andy Jassy throws towards Oracle.

Moore's law is, but the cost of a given amount of computational ability is still going down quickly.

What are your results like? What did you hope to accomplish when you started, and what actually happened? Can you name some of the biggest benefits and some of the biggest pitfalls?

So two different Districts, basically?

Can someone explain why Microsoft doesn't have to but Google does?

It took several attempts at doubling down on the deception (riding the course on her bike and posting the Strava trace) and being repeatedly called out before she gave up and admitted it.

Not nearly as laudable as admitting it as soon as someone accused her of cheating.

One of the things about human software engineers is that they can make assumptions based on what the system is for. For example you may say that "this system has to accept payments from counterparties" and they will intuitively know that they are dealing with people's money, and to be careful of situations like double billing and the like.

To me the most interesting thing that came out of this article was exponential backoff-retry. I've always used e (natural log) as the base for my exponential backoff, and never used jitter (all my apps are single clients that are just trying to hit the AWS API, and none run simultaneously and I don't own the other side of it).

By looking it up I learned the concept of jitter, which is how Ethernet works, and I think it's really cool.

Well it's all carbs. I don't see how adding water changes the macronutrient makeup.

A big part of it is going to be whether major cloud providers adopt these.

Didn't he fund Hulk Hogan's lawsuit against Gawker which essentially put that horrible rag out of business?