<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>2025/11 on Serenity | The intervention consultancy for struggling software teams</title><link>https://serenity.software/articles/2025/11/</link><description>Recent content in 2025/11 on Serenity | The intervention consultancy for struggling software teams</description><generator>Hugo</generator><language>en-US</language><copyright>© Serenity Software</copyright><lastBuildDate>Thu, 20 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://serenity.software/articles/2025/11/feed.xml" rel="self" type="application/rss+xml"/><item><title>Energy Management Beats Time Management in Engineering</title><link>https://serenity.software/articles/energy-management-beats-time-management-in-engineering/</link><pubDate>Thu, 20 Nov 2025 00:00:00 +0000</pubDate><guid>https://serenity.software/articles/energy-management-beats-time-management-in-engineering/</guid><description>&lt;p&gt;If you look at a standard burn-down chart or a timesheet, software development looks deceptively linear. One hour of coding equals one unit of output. If a project is falling behind, the &amp;ldquo;logical&amp;rdquo; management solution is to add more hours, ask the team to stay late, work a weekend, or squeeze in &amp;ldquo;just one more ticket&amp;rdquo; before the sprint closes. Or if you have the payroll, add more engineers.&lt;/p&gt;
&lt;p&gt;But anyone who has actually written code knows this is a lie.&lt;/p&gt;</description></item><item><title>Excellence is a Habit: Why Shipping Software Beats Perfection</title><link>https://serenity.software/articles/shipping-beats-perfection/</link><pubDate>Mon, 17 Nov 2025 00:00:00 +0000</pubDate><guid>https://serenity.software/articles/shipping-beats-perfection/</guid><description>&lt;p&gt;The urge to &amp;ldquo;rewrite it all&amp;rdquo; is often disguised as a pursuit of excellence.&lt;/p&gt;
&lt;p&gt;We’ve all seen the pattern. An engineer opens a file and becomes allergic to what they see. Maybe it’s messy legacy code, a &amp;ldquo;temporary&amp;rdquo; hack that is now celebrating its third birthday, or an architectural pattern that no longer fits the scale of the application.&lt;/p&gt;
&lt;p&gt;The instinct is to fix it. To overhaul it. To make it clean, modern, and &amp;ldquo;right.&amp;rdquo; This is a good instinct! We &lt;em&gt;should&lt;/em&gt; seek to improve things as we go, and developing that conscientiousness is vital for any senior engineer.&lt;/p&gt;</description></item><item><title>"Why Is Everything So Slow?", and how to fix it with Lead Time</title><link>https://serenity.software/articles/lead-time-why-is-everything-so-slow/</link><pubDate>Tue, 11 Nov 2025 00:00:00 +0000</pubDate><guid>https://serenity.software/articles/lead-time-why-is-everything-so-slow/</guid><description>&lt;p&gt;Everything feels…slow. You have an idea, or a critical feature, or an urgent bug fix, but it takes forever to send it through the process. Half the time it feels like it’s not even going through the process, it just dies on someone’s desk. Vanishing into the black box for weeks or months is a silent killer, and it’s both frustrating and disrespectful for anyone who’s making requests/demands on an engineering team.&lt;/p&gt;</description></item></channel></rss>