<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Experience on DevOps Noldus</title><link>https://blog.antnsn.dev/tags/developer-experience/</link><description>Recent content in Developer Experience on DevOps Noldus</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 08 Apr 2026 14:00:00 +0100</lastBuildDate><atom:link href="https://blog.antnsn.dev/tags/developer-experience/index.xml" rel="self" type="application/rss+xml"/><item><title>RRE: the weekly reflection framework I built for my team</title><link>https://blog.antnsn.dev/2026-p5-rre-weekly-reflection-framework/</link><pubDate>Wed, 08 Apr 2026 14:00:00 +0100</pubDate><guid>https://blog.antnsn.dev/2026-p5-rre-weekly-reflection-framework/</guid><description>&lt;p&gt;Engineers care deeply about observability. We instrument systems, build dashboards, define SLOs, and set up alerts. Because a system you can&amp;rsquo;t see is a system you can&amp;rsquo;t improve. We&amp;rsquo;d never run production infrastructure without telemetry.&lt;/p&gt;
&lt;p&gt;Then we run teams with no telemetry at all.&lt;/p&gt;
&lt;p&gt;No signal on whether the week moved things forward. No structured way to surface blockers early. No feedback loop that converts experience into better execution. Just meetings, Slack noise, and the vague sense that things are either fine or not fine.&lt;/p&gt;</description></item></channel></rss>