<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: EuanReid</title><link>https://news.ycombinator.com/user?id=EuanReid</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 27 Jun 2026 01:23:23 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=EuanReid" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by EuanReid in "The Oxford Comma – Why and Why Not (2024)"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Thu, 26 Mar 2026 19:04:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=47534349</link><dc:creator>EuanReid</dc:creator><comments>https://news.ycombinator.com/item?id=47534349</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47534349</guid></item><item><title><![CDATA[New comment by EuanReid in "I asked Claude for 37,500 random names, and it can't stop saying Marcus"]]></title><description><![CDATA[
<p>I suppose it appears a bunch in training data. Marcus Aurelius and Marcus Crassus get mentioned a lot through history.</p>
]]></description><pubDate>Wed, 25 Feb 2026 19:27:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=47156532</link><dc:creator>EuanReid</dc:creator><comments>https://news.ycombinator.com/item?id=47156532</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47156532</guid></item><item><title><![CDATA[New comment by EuanReid in "Osaka: Kansai Airport proud to have never lost single piece of luggage (2024)"]]></title><description><![CDATA[
<p>Headline's a bit misleading. They've never <i>permanently</i> lost a bag, and well done to them for that, but they've certainly lost them for periods of time. Just eventually found them.</p>
]]></description><pubDate>Tue, 24 Feb 2026 17:06:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=47139551</link><dc:creator>EuanReid</dc:creator><comments>https://news.ycombinator.com/item?id=47139551</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47139551</guid></item><item><title><![CDATA[New comment by EuanReid in "1 kilobyte is precisely 1000 bytes?"]]></title><description><![CDATA[
<p>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).</p>
]]></description><pubDate>Tue, 03 Feb 2026 18:33:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=46875122</link><dc:creator>EuanReid</dc:creator><comments>https://news.ycombinator.com/item?id=46875122</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46875122</guid></item><item><title><![CDATA[New comment by EuanReid in "Ask HN: What tone to use in code review suggestions?"]]></title><description><![CDATA[
<p>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"<p>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.</p>
]]></description><pubDate>Mon, 27 Jun 2022 16:44:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=31897159</link><dc:creator>EuanReid</dc:creator><comments>https://news.ycombinator.com/item?id=31897159</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31897159</guid></item></channel></rss>