<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Chris Worth</title><link>https://chrisworth.dev/skill-tag/infrastructure/</link><description>Recent content in Infrastructure on Chris Worth</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 23 Mar 2025 18:00:00 -0600</lastBuildDate><atom:link href="https://chrisworth.dev/skill-tag/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Lean Development Environment on Arch Linux</title><link>https://chrisworth.dev/posts/arch-linux-development-environment-guide/</link><pubDate>Sun, 23 Mar 2025 18:00:00 -0600</pubDate><guid>https://chrisworth.dev/posts/arch-linux-development-environment-guide/</guid><description>&lt;p>Development environments often accumulate bloat over time. Hidden services consume resources, background processes you didn&amp;rsquo;t authorize run constantly, and update mechanisms interrupt workflow at the worst possible moments. After years of managing enterprise systems and implementing automation solutions, I found that traditional distributions introduced unnecessary complexity that directly impacted development efficiency.&lt;/p>
&lt;p>The problem became clear when I noticed development machines taking 30+ seconds to boot, consuming gigabytes of RAM before opening a single application, and running dozens of services irrelevant to actual development work. The solution: a lean, transparent system where every component serves a clear purpose.&lt;/p></description></item></channel></rss>