<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Benchmarks on Romi's Dev Journey</title><link>https://romisugi.dev/tags/benchmarks/</link><description>Recent content in Benchmarks on Romi's Dev Journey</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 02 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://romisugi.dev/tags/benchmarks/index.xml" rel="self" type="application/rss+xml"/><item><title>How I Learned to Use Python's Time Module</title><link>https://romisugi.dev/posts/python-tips/python-time-module-guide/</link><pubDate>Sat, 02 Aug 2025 00:00:00 +0000</pubDate><guid>https://romisugi.dev/posts/python-tips/python-time-module-guide/</guid><description>&lt;p>Remember how I shared how Enums saved me from string typos? Well, I recently had another &amp;ldquo;aha!&amp;rdquo; moment with Python&amp;rsquo;s &lt;code>time&lt;/code> module. What seemed like a boring collection of time functions actually solved real headaches in my automation scripts!&lt;/p>
&lt;p>Let me show you how understanding these tools made my scripts more precise and reliable - just like Enums did for my code quality.&lt;/p>
&lt;h2 id="the-problem-my-scripts-timing-was-all-wrong">The Problem: My Script&amp;rsquo;s Timing Was All Wrong&lt;/h2>
&lt;p>I used to rely solely on &lt;code>time.time()&lt;/code> for everything - measuring durations, logging timestamps, you name it. Then one day, my scheduled tasks started acting weird:&lt;/p></description></item></channel></rss>