erik_seaberg

It’s better to quote a reserved word than to be unable to use it.

Seems to me the article focused on how they did this big job, rather than why.

There are times when mistakes will cause more serious problems for customers. There are times when staff will be less available to aid recovery. A good strategy shouldn't deny these truths.

Will the compiler infer that a lambda or a method ref implements Func with its exception type param, or do you have to rewrite call sites?

Software demand skyrocketed because of the WWW, which came out in 1991 just before Python (although Perl, slightly more mature, saw more use in the early days).

Deep work needs peace and quiet. This is getting hard to find in an open plan office, except late in the evening.

This. It's so frustrating that sync.Map isn't generic and reusing the builtin map API is impossible.

Boring repetition is a bad fit for the human brain. Working memory is very small. Mistakes per line are frequent. It wants to see patterns that are not quite there. Even when it works out, it's millions of times slower than having the computer fill in grunt work from a more concise and readable spec of the problem.

Around competitive prices and terms rather than a monopoly.

It might seem really unlikely any acquirer would ever sue, but if your big company has compliance auditors they will need to see something in black and white.

The warning went at least as far as the inland side of Fremont, which seemed extreme.

Pairing doesn't replace code review because the reviewer needs to see the finished branch with fresh eyes, unbiased by discussion and false starts, to know whether it's safe and clearly explained in writing for every oncall in the future.

(I also need peace and quiet to think.)

A "trusted team" pushing unreviewed code to prod is breathtakingly reckless. I don't trust anyone to do that. Not even myself. Please review my code, because our customers matter and so does oncall's peace and quiet.

On svn we reviewed finished feature branches and merged them to the next release branch every few days, though svn routinely crapped itself on spurious conflicts like renames. Git just enables this reliably.