<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Ryan Ressmeyer</title><link>https://ryanressmeyer.com/blog/</link><description>Recent content in Blog on Ryan Ressmeyer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ryanressmeyer.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Researchers: ditch conda, embrace uv</title><link>https://ryanressmeyer.com/blog/researchers-ditch-conda-embrace-uv/</link><pubDate>Sun, 05 Oct 2025 00:00:00 +0000</pubDate><guid>https://ryanressmeyer.com/blog/researchers-ditch-conda-embrace-uv/</guid><description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://ryanressmeyer643428.substack.com/p/researchers-ditch-conda-embrace-uv"&gt;Substack&lt;/a&gt; on October 5, 2025.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re a graduate student like me who writes a lot of code and you haven&amp;rsquo;t
read Patrick Mineault&amp;rsquo;s &lt;a href="https://goodresearch.dev/"&gt;Good Research Code Handbook&lt;/a&gt;,
I highly recommend it. It&amp;rsquo;s an approachable guide built on a simple premise:
organizing your code saves you from frustration, makes your research more
reproducible, and, most importantly, frees up your limited mental energy to
focus on actual research problems. How you structure your code is how you
think, and skipping a 30-minute project setup can cost you hours of refactoring
later.&lt;/p&gt;</description></item></channel></rss>