<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chaos as Code</title><link>https://chaos-as-code.de/</link><description>Recent content on Chaos as Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 23:00:00 +0200</lastBuildDate><atom:link href="https://chaos-as-code.de/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://chaos-as-code.de/about/</link><pubDate>Wed, 30 Sep 2026 23:00:00 +0200</pubDate><guid>https://chaos-as-code.de/about/</guid><description>&lt;p&gt;Hi there. Somehow you made it here and even clicked on the &amp;lsquo;About&amp;rsquo; link. Wow. So, here we go. I am a software developer, DevOps engineer and administrator. Well, kind of all of those things. It grew over time: I started as an administrator, later studied computer science, and here we are.&lt;/p&gt;&#10;&lt;h2 id="but-why"&gt;But why?&lt;/h2&gt;&#10;&lt;p&gt;If you ask me, the most important thing I learned in my studies came from my software engineering professor. She once said: &amp;ldquo;If you take one thing from this module, let it be this: Always ask &amp;lsquo;Why?&amp;rsquo;&amp;rdquo; In her view, the real source of truth lies in answering the question: &amp;ldquo;Why do you do this? Why do you want that? Why do you behave like that?&amp;rdquo; Of course, this was in the context of software engineering, and therefore requirements management. But I think she hit the nail on the head, not only for software engineering, but for a lot of other things too. So this raises the question: Why write a blog?&lt;/p&gt;</description></item><item><title>A headless gaming PC or: how I moved my gaming machine to the rack</title><link>https://chaos-as-code.de/posts/headless-gaming-pc/</link><pubDate>Fri, 25 Sep 2026 11:20:34 +0200</pubDate><guid>https://chaos-as-code.de/posts/headless-gaming-pc/</guid><description>&lt;h2 id="the-problem-and-the-idea"&gt;The problem and the idea&lt;/h2&gt;&#10;&lt;p&gt;Using a high-performance gaming machine brings lots of joy (in gaming) and other benefits (in development), but also the fundamental problem of high power consumption, even when there is no load on the machine.&lt;/p&gt;&#10;&lt;p&gt;To get an idea, here are some numbers: approximately 185 watts of power consumption for the whole desk setup (this means the PC, monitor, attached peripherals, lights, etc.), while only a browser and a media stream (Jellyfin) are active. Nothing special, the machine is bored by this. But still, 185 watts. This adds up fast.&lt;/p&gt;</description></item></channel></rss>