<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Simon Aronsson</title><link>https://simme.dev/</link><description>Recent content on Simon Aronsson</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://simme.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>The end of "Just ask Sarah"</title><link>https://simme.dev/posts/the-end-of-just-ask-sarah/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/the-end-of-just-ask-sarah/</guid><description>Documentation used to back up organizational memory. With agents, it becomes execution context.</description></item><item><title>What I'm doing now.</title><link>https://simme.dev/now/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/now/</guid><description>&lt;h2 id="building"&gt;Building&lt;/h2&gt;
&lt;p&gt;This week I&amp;rsquo;ve decided to focus on writing, so there are no exciting project updates to report.&lt;/p&gt;
&lt;h2 id="reading"&gt;Reading&lt;/h2&gt;
&lt;p&gt;A &lt;a href="https://cmustrudel.github.io/papers/msr2026he.pdf"&gt;paper&lt;/a&gt; by the good folks at STRUDEL on how the speed of agentic development might come at the cost of quality.&lt;/p&gt;</description></item><item><title>Boring code is an organizational tell</title><link>https://simme.dev/posts/boring-code-is-an-organizational-tell/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/boring-code-is-an-organizational-tell/</guid><description>Why clever code is an organizational output, not an engineering one — and how agents turn a slow-moving problem into a fast one.</description></item><item><title>What happens if you give an AI agent a home instead of a session?</title><link>https://simme.dev/posts/what-happens-if-you-give-an-ai-agent-a-home-instead-of-a-session/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/what-happens-if-you-give-an-ai-agent-a-home-instead-of-a-session/</guid><description>My design goals for building an autonomous AI agent, rather than limiting it to
interactive prompting session-by-session.</description></item><item><title>COS Lite Machine Sizer</title><link>https://simme.dev/posts/cos-lite-machine-sizer/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/cos-lite-machine-sizer/</guid><description>A sizing tool for COS Lite deployments. It used to live here but got lost in one of my many blog migrations. Now it&amp;rsquo;s back!</description></item><item><title>Building a Dry-Run Mode for the OpenTelemetry Collector</title><link>https://simme.dev/posts/building-a-dry-run-mode-for-the-opentelemetry-collector/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/building-a-dry-run-mode-for-the-opentelemetry-collector/</guid><description>Signal Studio explores a deficit in the OpenTelemetry ecosystem: how to assess the impact
of changes to your config.yaml &lt;em&gt;before&lt;/em&gt; rolling out in production.</description></item><item><title>How I built this page</title><link>https://simme.dev/posts/building-this-page/</link><pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/building-this-page/</guid><description>This site has needed a facelift for years. Not because the technology was outdated, but because
every previous version of this blog eventually died. Quietly.</description></item><item><title>Observability is becoming mission critical, but who watches the watchmen?</title><link>https://simme.dev/posts/who-watches-the-watchmen/</link><pubDate>Wed, 14 Sep 2022 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/who-watches-the-watchmen/</guid><description>The last couple of years, there has been quite a lot of development lowering the barrier of entry
for observability. There are now quite a few, reasonably mature options out there that lets you set
up a good monitoring stack either through a few clicks or by a few one-liners in the terminal.</description></item><item><title>Error Economics - How to avoid breaking the budget</title><link>https://simme.dev/posts/error-economics/</link><pubDate>Fri, 27 Aug 2021 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/error-economics/</guid><description>At SLOConf 2021 I talked about how we may use error budgets to add pass/fail criterias to reliability tests we run as part of our CI pipelines.</description></item><item><title>On shaming and blaming</title><link>https://simme.dev/posts/on-shaming-and-blaming/</link><pubDate>Sat, 21 Dec 2019 00:00:00 +0000</pubDate><guid>https://simme.dev/posts/on-shaming-and-blaming/</guid><description>There are severe consequences of allowing shaming and blaming in your engineering culture. In this
essay, I&amp;rsquo;ll suggest a few small things you can do instead.</description></item><item><title>About</title><link>https://simme.dev/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://simme.dev/about/</guid><description>&lt;h2 id="what-i-work-on"&gt;What I work on&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;m an engineering leader from eu-north-1 working at Canonical, where I focus on making observability accessible and valuable for teams of any size.&lt;/p&gt;
&lt;p&gt;My background is in open-source, developer communities, and building teams that ship.&lt;/p&gt;
&lt;p&gt;I spend most of my time on the boring end of the problem: how to keep systems understandable as they grow, how to make on-call something a team can sustain, and how to make sure engineers can assess the reliability and availability of what they produce.&lt;/p&gt;</description></item><item><title>Resume</title><link>https://simme.dev/resume/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://simme.dev/resume/</guid><description/></item></channel></rss>