<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logging on Arhuman's Blog</title><link>https://blog.assad.fr/en/tags/logging/</link><description>Recent content in Logging on Arhuman's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 13 Sep 2026 10:30:00 +0200</lastBuildDate><atom:link href="https://blog.assad.fr/en/tags/logging/index.xml" rel="self" type="application/rss+xml"/><item><title>The Logging Dilemma</title><link>https://blog.assad.fr/en/post/log-dilemma/</link><pubDate>Sun, 13 Sep 2026 10:30:00 +0200</pubDate><guid>https://blog.assad.fr/en/post/log-dilemma/</guid><description>&lt;p&gt;Every developer has lived through this scene: the adrenaline spike when a production incident is announced. That mix of dread about what you are going to find and frenzy to collect any piece of information that will let you understand and then fix the problem. It happened to me again a few days ago. I can still picture myself rushing to the logs, and I still remember the frustration of finding nothing but basic information and an unhelpful error message: &amp;ldquo;Unable to load cache&amp;rdquo;.&lt;/p&gt;</description></item></channel></rss>