<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CLI on Yet another trashy dev blog</title><link>https://blog.kalilarosa.xyz/categories/cli/</link><description>Recent content in CLI on Yet another trashy dev blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 12 Sep 2025 16:32:16 -0500</lastBuildDate><atom:link href="https://blog.kalilarosa.xyz/categories/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing Egg.</title><link>https://blog.kalilarosa.xyz/posts/introducing-egg/</link><pubDate>Mon, 05 May 2025 10:14:54 -0500</pubDate><guid>https://blog.kalilarosa.xyz/posts/introducing-egg/</guid><description>&lt;h1 id="because-i-can"&gt;Because I can.&lt;/h1&gt;&#10;&lt;p&gt;Everyone always tells you &amp;ldquo;don&amp;rsquo;t reinvent the wheel.&amp;rdquo; Use existing frameworks. Don&amp;rsquo;t waste time building what already exists. And they&amp;rsquo;re probably right for most people, most of the time. You aren&amp;rsquo;t going to do it any better than x engineers.&lt;/p&gt;&#10;&lt;p&gt;But sometimes you need to prove to yourself (and any future potential employers) that you can actually build the wheel. Sometimes the best way to understand production-ready software is to build it yourself, exactly the way you want it to work. Sometimes problem-solving IS the point.&lt;/p&gt;</description></item></channel></rss>