I agree that suddenly adding a formatter to existing code could be disruptive. But how does "buy in from the team" work over time? If you hire someone new and they don't like the format rules, do you stop using the formatter?

+1

For example, "nit: maybe call the function updateCreditCard instead of updateCard"

If you disagree and think your function name is better (or that the two are equally bad), then I'm happy to go along with what you've got. But maybe you didn't think of this name or maybe I've convinced you. Either it's a quick fix (and no re-review needed) or you just dismiss my comment.

> As an American, a lot of UK geography and history questions are beyond my ken

But note that the UK-based contestants have no problem with sequences like "US vice presidents ordered by number of terms served" or "US capitals ordered alphabetically by the state they're in".

That's covered in the blog post:

First, that archers can actually be more effective against mounted troops than foot: the mounted troops ride close together, horses are hard to fully armor, and one horse getting hit in the leg can cause a lot of chaos.

Second, at Agincourt, the French knights _walked_ through the arrow-fire quite successfully, but the effort (physical, mental, cumulative effect of small wounds) tired them enough that the English soldiers could beat them hand-to-hand. And that this ability to inflict small damage before the main fighting is why archers were valuable.

"Maybe the memes making fun of this person are, in fact, an exaggeration."

Sure. I don't need much convincing that Ballmer was only "bad" rather than "uniquely terrible". It seems a pretty normal thing that the negative reaction was outsized.

But I also think it would be more interesting to look at cases where the reaction by the haters was _spot on_. Or even where it _undersold_ how bad things were.