<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tech Debt on Rough Edges</title><link>https://roughedges.dev/tags/tech-debt/</link><description>Recent content in Tech Debt on Rough Edges</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 16 Jun 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://roughedges.dev/tags/tech-debt/index.xml" rel="self" type="application/rss+xml"/><item><title>When Leaders Ignore the No Asshole Rule</title><link>https://roughedges.dev/posts/when-leaders-ignore-the-no-asshole-rule/</link><pubDate>Tue, 16 Jun 2026 00:00:00 -0400</pubDate><guid>https://roughedges.dev/posts/when-leaders-ignore-the-no-asshole-rule/</guid><description>&lt;p&gt;There&amp;rsquo;s a pattern I&amp;rsquo;ve watched play out in more than one organization. From a distance it looks like high performance. Up close it&amp;rsquo;s something else.&lt;/p&gt;
&lt;p&gt;A strong engineer – relentless, demonstrably capable, the kind of person who ships when others stall – has the ear of the CTO. The project is high-stakes. Delivery feels close. And the closer it gets, the more the engineer&amp;rsquo;s behavior gets defended, smoothed over, accommodated. Process is bypassed because process is slow. Other teams who push back get reframed as obstacles. Guardrails that applied yesterday no longer apply. The CTO, who is genuinely well regarded, has decided that this is what it takes to win.&lt;/p&gt;</description></item></channel></rss>