<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Green Programming on No Semicolons</title><link>https://nosemicolons.com/tags/green-programming/</link><description>Recent content in Green Programming on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Oct 2026 14:07:12 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/green-programming/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Energy Bill: How I Cut My Development Carbon Footprint by 75% (While Building 3x More Features)</title><link>https://nosemicolons.com/posts/ai-code-generation-energy-efficiency-carbon-footprint/</link><pubDate>Sat, 10 Oct 2026 14:07:12 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-energy-efficiency-carbon-footprint/</guid><description>&lt;p>Ever wondered if your AI coding assistant is secretly burning through the equivalent of a small town&amp;rsquo;s power grid? I sure did, especially after my monthly electricity bill started looking like a phone number.&lt;/p>
&lt;p>Three months ago, I decided to dig deep into the energy costs of AI-assisted development. What I found surprised me: with the right approach, AI tools can actually &lt;em>reduce&lt;/em> your overall development carbon footprint significantly. Here&amp;rsquo;s how I cut my energy consumption by 75% while tripling my feature output.&lt;/p></description></item></channel></rss>