<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Links on hxmn.dev</title><link>https://hxmn.dev/tags/links/</link><description>Recent content in Links on hxmn.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2026 09:00:00 +0300</lastBuildDate><atom:link href="https://hxmn.dev/tags/links/index.xml" rel="self" type="application/rss+xml"/><item><title>Links — April 2026</title><link>https://hxmn.dev/links/2026-04/</link><pubDate>Wed, 15 Apr 2026 09:00:00 +0300</pubDate><guid>https://hxmn.dev/links/2026-04/</guid><description>&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;How We Reduced Our CI Build Time by 70%&lt;/a&gt;&lt;/strong&gt; — Shopify engineering on parallelizing tests, caching dependencies, and splitting their monorepo build. The section on test partitioning by historical duration is worth stealing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://go.dev/ref/mem" target="_blank" rel="noopener"
 &gt;The Go Memory Model&lt;/a&gt;&lt;/strong&gt; — Re-read this every year. If you are using channels or atomics, this is the spec that tells you what is actually guaranteed.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;Designing Data-Intensive Applications — Chapter 9 (free excerpt)&lt;/a&gt;&lt;/strong&gt; — Kleppmann on consistency and consensus. Dense but essential. Good companion to the Jepsen posts.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;SQLite Is Not a Toy Database&lt;/a&gt;&lt;/strong&gt; — Makes the case for SQLite as a production database for read-heavy workloads. The benchmarks against PostgreSQL for single-node deployments are surprising.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;Structured Logging in Go with slog&lt;/a&gt;&lt;/strong&gt; — Practical walkthrough of the &lt;code&gt;log/slog&lt;/code&gt; package introduced in Go 1.21. Good coverage of custom handlers and performance implications.&lt;/p&gt;</description></item><item><title>Links — March 2026</title><link>https://hxmn.dev/links/2026-03/</link><pubDate>Sat, 28 Mar 2026 09:00:00 +0300</pubDate><guid>https://hxmn.dev/links/2026-03/</guid><description>&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;The Platform Engineering Maturity Model&lt;/a&gt;&lt;/strong&gt; — Thoughtful framework for evaluating where your platform org sits. Useful for building the case for investment without overselling.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;How Postgres Stores Rows&lt;/a&gt;&lt;/strong&gt; — Deep dive into heap tuples, TOAST, and page layout. Understanding this makes VACUUM and bloat much less mysterious.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;Writing Docs That People Actually Read&lt;/a&gt;&lt;/strong&gt; — Stripe&amp;rsquo;s documentation lead on structure, examples-first writing, and why API reference is not enough. Changed how I think about README files.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;Prometheus: The Documentary&lt;/a&gt;&lt;/strong&gt; — History of Prometheus from the SoundCloud days to CNCF graduation. Good context for understanding why it works the way it does.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a class="link" href="https://example.com" target="_blank" rel="noopener"
 &gt;Error Handling in Rust: A Deep Dive&lt;/a&gt;&lt;/strong&gt; — Even if you do not write Rust, the taxonomy of error types (recoverable vs. fatal, expected vs. unexpected) is universally applicable.&lt;/p&gt;</description></item></channel></rss>