<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Source on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/categories/open-source/</link><description>Recent content in Open Source on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 04 Jun 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/categories/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>CleanCLI: Building a Faster, Cleaner PowerShell Experience</title><link>https://drlongnecker.com/blog/2026/06/cleancli-powershell-terminal-experience/</link><pubDate>Thu, 04 Jun 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/06/cleancli-powershell-terminal-experience/</guid><description>&lt;p&gt;For most developers and sysadmins, terminal customization starts innocently.&lt;/p&gt;
&lt;p&gt;You tweak the prompt, then add a helper function, then pull in a theme framework. Maybe install OhMyPosh/OhMyZsh or a few PSReadLine plugins. A year later your PowerShell profile has become a small ecosystem with internet dependencies, startup overhead, random helper scripts from 2010 (&amp;hellip; I might need that random script!), and enough conditional logic to qualify as infrastructure.&lt;/p&gt;
&lt;p&gt;Mine certainly did.&lt;/p&gt;</description></item></channel></rss>