<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>O11y on It Might be Working</title><link>https://iguessthatworks.com/tags/o11y/</link><description>Recent content in O11y on It Might be Working</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Jeff Mayeur</copyright><lastBuildDate>Tue, 14 Jul 2026 07:00:00 -0700</lastBuildDate><atom:link href="https://iguessthatworks.com/tags/o11y/index.xml" rel="self" type="application/rss+xml"/><item><title>If I Knew, What Good Can I Do?</title><link>https://iguessthatworks.com/posts/07-2026/pixel/</link><pubDate>Tue, 14 Jul 2026 07:00:00 -0700</pubDate><guid>https://iguessthatworks.com/posts/07-2026/pixel/</guid><description>
&lt;p&gt;Oh what I would do, if only I knew...&lt;/p&gt;
&lt;p&gt;Logging has been a continuously evolving practice for me. When I started writing code, I leaned heavily into debug/log/assert hack based strategies. I view logging as something that would help me solve a production issue, something that only temporarily invaded the code. I was a very junior developer, so it made sense that my view of traceability was limited to the scope of the system I was focused on.&lt;/p&gt;</description></item></channel></rss>