https://odhyp.com/Writings on automation, data visualization, and web development.en-usHugohttps://odhyp.com/writings/goodbye-pip-hello-uv/https://odhyp.com/writings/goodbye-pip-hello-uv/Mon, 23 Jun 2025 17:04:12 +0700hello@odhyp.com (Odhy Pradhana)<p>I’ve been trying out the new <code>uv</code> from <a href="https://github.com/astral-sh">Astral</a> for managing my Python project. It’s fast, simple, and honestly makes the usual <code>pip</code> + <code>venv</code> setup feel kinda clunky. So, I figured I’d write this down since I’m switching my Python project over to <code>uv</code>.</p>
<h2 id="why-even-switch">Why even switch?</h2>
<p>Python’s tooling has always been a bit… scattered. You install stuff with <code>pip</code>, manage environments with <code>venv</code>, freeze those with <code>pip-tools</code>, or lock them using <code>poetry</code>. Each tool solves part of the problem, but juggling all of them gets tiresome fast.</p>https://odhyp.com/writings/upgrading-a-hugo-website-from-tailwind-css-v3-to-v4/https://odhyp.com/writings/upgrading-a-hugo-website-from-tailwind-css-v3-to-v4/Thu, 13 Feb 2025 00:00:00 +0000hello@odhyp.com (Odhy Pradhana)<p>I recently upgraded my site to use TailwindCSS v4. In this post, I’ll guide you through the upgrade process, just as I did for my own website, step by step… hopefully.</p>
<p>There are a few breaking changes, as stated in their <a href="https://tailwindcss.com/docs/upgrade-guide">documentation</a>. Some of these will change the way we structure the Hugo project.</p>
<ul>
<li>
<p>TailwindCSS v4 now automatically detects the content directory unlike the previous version, where we manually listed the <code>layouts</code> and <code>contents</code> files.</p>