<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on R055LE</title><link>https://r055le.github.io/post/</link><description>Recent content in Posts on R055LE</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026, R055LE; all rights reserved.</copyright><lastBuildDate>Sun, 12 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://r055le.github.io/post/index.xml" rel="self" type="application/rss+xml"/><item><title>The Invisible Portfolio</title><link>https://r055le.github.io/post/the-invisible-portfolio/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://r055le.github.io/post/the-invisible-portfolio/</guid><description>
&lt;p&gt;DevOps is invisible work. Not &amp;quot;underappreciated&amp;quot; invisible — invisible by design. The ideal day in operations is the one where nothing happens. Your alerting stays quiet, your deployments roll out, your infrastructure handles the spike because you sized it right six months ago. Nobody thanks you for the incident that didn't happen. And the day you finally leave it a well-oiled machine? That's invisible too.&lt;/p&gt;
&lt;p&gt;This creates a problem when someone asks what you've been doing for the last 13 years.&lt;/p&gt;</description></item></channel></rss>