<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python on Samuel Matildes - Knowledge Base</title><link>https://docs.matildes.dev/tags/python/</link><description>Recent content in Python on Samuel Matildes - Knowledge Base</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 26 May 2026 14:15:13 +0100</lastBuildDate><atom:link href="https://docs.matildes.dev/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Export Windows EVTX to CSV with evtxparser</title><link>https://docs.matildes.dev/windows/admin/evtxparser/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/windows/admin/evtxparser/</guid><description>&lt;p&gt;
 &lt;a href="https://github.com/samatild/evtxparser" target="_blank" rel="noopener"&gt;
 &lt;i class="fab fa-github" aria-hidden="true"&gt;&lt;/i&gt; GitHub
 &lt;/a&gt;
 &amp;nbsp;•&amp;nbsp;
 &lt;a href="https://pypi.org/project/evtxparser/" target="_blank" rel="noopener"&gt;
 &lt;i class="fab fa-python" aria-hidden="true"&gt;&lt;/i&gt; PyPI
 &lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;&lt;i class="fas fa-file-alt" aria-hidden="true"&gt;&lt;/i&gt; Export Windows Event Viewer &lt;code&gt;.evtx&lt;/code&gt; logs to clean CSV output without dragging a GUI into the workflow.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://docs.matildes.dev/windows/admin/evtxparser/images/evtxparser.png" alt="evtxparser example"&gt;&lt;/p&gt;
&lt;h2 id="what-is-evtxparser"&gt;What is evtxparser?&lt;a class="td-heading-self-link" href="#what-is-evtxparser" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://github.com/samatild/evtxparser"&gt;&lt;code&gt;evtxparser&lt;/code&gt;&lt;/a&gt; is a focused Python CLI for exporting Windows &lt;code&gt;.evtx&lt;/code&gt; files to CSV. It is designed for the cases where you do not want a full GUI workflow or a heavyweight parsing pipeline: open the log, stream records, and write rows immediately.&lt;/p&gt;</description></item><item><title>Before You Scale: Why Software Optimization Beats Hardware Every Time</title><link>https://docs.matildes.dev/software-engineering/memory-optimization/</link><pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/software-engineering/memory-optimization/</guid><description>&lt;p&gt;&lt;i class="fas fa-microchip" aria-hidden="true"&gt;&lt;/i&gt; Before You Scale: Why Software Optimization Beats Hardware Every Time&lt;/p&gt;
&lt;h2 id="summary"&gt;Summary&lt;a class="td-heading-self-link" href="#summary" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When your application crashes with an Out-of-Memory (OOM) error, the instinctive response is often: &amp;ldquo;Let&amp;rsquo;s add more RAM.&amp;rdquo; In the age of cloud computing where resources are just a slider away, this approach has become the default. But what if I told you that a 30-minute code investigation could reduce your memory usage by &lt;strong&gt;95%&lt;/strong&gt;—turning a 3GB memory spike into 150MB?&lt;/p&gt;</description></item></channel></rss>