EuanReid

Perhaps something requiring opt-in sooner, so project maintainers can - through config - say "we don't use the pip interface on this project"?

A web and mobile app for tracking cellar contents that doesn't feel dated or clunky, and with which I can make assorted dynamically-updating menus for different use cases. I'll probably do a Show HN once it's live.

I've generally found DeepSWE[0] to be pretty true to reality.

[0]: https://deepswe.datacurve.ai/

There are so many times the Oxford comma prevents ambiguity. I have yet to see a counterexample. Commas separate list entries, don't change it for the last one.

I suppose it appears a bunch in training data. Marcus Aurelius and Marcus Crassus get mentioned a lot through history.

Headline's a bit misleading. They've never permanently lost a bag, and well done to them for that, but they've certainly lost them for periods of time. Just eventually found them.

Upper-K is for Kelvin, so can't be mixed in as a prefix in case someone decides to commit physics crimes and talk about temperature-mass (Kkg).

Obviously tone is hard in text, and it's worse in multilingual teams. What's been very effective for my current team is adding explicit context as a comment prefix with standardised terms: - Nit for "it doesn't actually matter" - Suggestion for "this approach might be better, what do you think?" - Question for "help me understand this" - Requested Change for "this is actually a blocker"

We include this expectation in our working agreement, stick to it rigorously for reviews where reviewer and reviewee haven't established a strong rapport yet, and use it as appropriate beyond that. So far we've had no confusion about tone in reviews.