<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>culture · Alex Moreno</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/tags/culture/</link><description>Alex Moreno writes about developer tools, calm software and the occasional home-lab adventure.</description><generator>Hugo</generator><language>en-US</language><managingEditor>hello@example.org (Alex Moreno)</managingEditor><lastBuildDate>Wed, 03 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/tags/culture/index.xml" rel="self" type="application/rss+xml"/><item><title>The quiet value of boring dependencies</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/boring-dependencies/</link><pubDate>Wed, 03 Sep 2025 00:00:00 +0000</pubDate><guid>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/boring-dependencies/</guid><description>&lt;p&gt;When I pick a library, I now ask three questions before I read the README.&lt;/p&gt;&#10;&lt;h2 id="how-old-is-it"&gt;How old is it?&lt;a class="anchor" href="#how-old-is-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;A library that has been maintained for ten years will probably be maintained next year. A library that appeared last month might not be.&lt;/p&gt;&#10;&lt;h2 id="how-small-is-it"&gt;How small is it?&lt;a class="anchor" href="#how-small-is-it" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Small dependencies are easy to read, easy to vendor, and easy to replace. Large ones become part of your architecture whether you like it or not.&lt;/p&gt;</description></item><item><title>Notes on code review etiquette</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/code-review-etiquette/</link><pubDate>Tue, 01 Oct 2024 00:00:00 +0000</pubDate><guid>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/code-review-etiquette/</guid><description>&lt;p&gt;A few habits that made my reviews kinder and faster.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Ask before you assert.&lt;/strong&gt; &amp;ldquo;What happens if this list is empty?&amp;rdquo; lands better than &amp;ldquo;This breaks on empty lists.&amp;rdquo;&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Label your nits.&lt;/strong&gt; If it&amp;rsquo;s optional, say so, and don&amp;rsquo;t block on it.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Approve improvements.&lt;/strong&gt; The bar is &lt;em&gt;better than before&lt;/em&gt;, not &lt;em&gt;perfect&lt;/em&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Review within a day.&lt;/strong&gt; A fast &amp;ldquo;not yet&amp;rdquo; beats a slow &amp;ldquo;looks good&amp;rdquo;.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="for-authors"&gt;For authors&lt;a class="anchor" href="#for-authors" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Small changes get better reviews. If a pull request needs a meeting to explain it, it&amp;rsquo;s probably two pull requests.&lt;/p&gt;</description></item></channel></rss>