<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Observability on Simple Enough Blog</title><link>https://blog-dev.simpleenough.net/tags/observability/</link><description>Recent content in Observability on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 25 Feb 2026 10:00:00 +0100</lastBuildDate><atom:link href="https://blog-dev.simpleenough.net/tags/observability/index.xml" rel="self" type="application/rss+xml"/><item><title>Everyday Chaos Engineering: Learning to Love the Wave</title><link>https://blog-dev.simpleenough.net/blog/wave/</link><pubDate>Wed, 25 Feb 2026 10:00:00 +0100</pubDate><guid>https://blog-dev.simpleenough.net/blog/wave/</guid><description>&lt;p>We all dream of a stable, predictable, “calm” system.
And yet, the reality of a modern platform is a living sea: deployments, external dependencies, cloud quotas, flaky networks, traffic spikes, human error—and sometimes… just “something” that should never have happened.&lt;/p>
&lt;p>Chaos engineering is often presented as a spectacular discipline—“we cut an AWS zone,” “we kill a cluster,” “we take Kafka down.”
In real life (and especially in small teams), that’s neither necessary nor desirable at the beginning.&lt;/p></description></item></channel></rss>