<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Blog</title>
    <link>https://codescene.com/blog</link>
    <description>A developer’s blog by Adam Tornhill. He is founder of CodeScene - a tool 
that gives developers better context and visibility into software projects.</description>
    <language>en</language>
    <pubDate>Wed, 03 Jun 2026 13:00:01 GMT</pubDate>
    <dc:date>2026-06-03T13:00:01Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Announcement: Deterministic PR Refactoring Agents</title>
      <link>https://codescene.com/blog/deterministic-pr-refactoring-agents</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/deterministic-pr-refactoring-agents" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/Featured%20image_Deterministic%20PR%20Refactoring%20Agents_1.png" alt="PR refactoring agent " class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;CodeScene’s new PR Refactoring Agent analyzes the branch using deterministic Code Health data, performs targeted refactorings, and commits improvements back to the PR.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span&gt;The result is code that’s easier to review, AI-friendly, and more token efficient. And yes, we support all those promises with data. Your code deserves that.&lt;/span&gt;&lt;/p&gt; 
&lt;p style="text-align: center; font-size: 14px;"&gt;&lt;em&gt;&lt;span&gt;Fix Code Health degradations via a single click in the PR.&lt;/span&gt;&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/deterministic-pr-refactoring-agents" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/Featured%20image_Deterministic%20PR%20Refactoring%20Agents_1.png" alt="PR refactoring agent " class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;CodeScene’s new PR Refactoring Agent analyzes the branch using deterministic Code Health data, performs targeted refactorings, and commits improvements back to the PR.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span&gt;The result is code that’s easier to review, AI-friendly, and more token efficient. And yes, we support all those promises with data. Your code deserves that.&lt;/span&gt;&lt;/p&gt; 
&lt;p style="text-align: center; font-size: 14px;"&gt;&lt;em&gt;&lt;span&gt;Fix Code Health degradations via a single click in the PR.&lt;/span&gt;&lt;/em&gt;&lt;/p&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Fdeterministic-pr-refactoring-agents&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AI Coding</category>
      <pubDate>Thu, 28 May 2026 18:23:03 GMT</pubDate>
      <guid>https://codescene.com/blog/deterministic-pr-refactoring-agents</guid>
      <dc:date>2026-05-28T18:23:03Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
    <item>
      <title>Unhealthy code is burning your token usage - here's the data</title>
      <link>https://codescene.com/blog/unhealthy-code-is-burning-your-token-usage-heres-the-data</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/unhealthy-code-is-burning-your-token-usage-heres-the-data" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/token_waste_1200x600.png" alt="Unhealthy code is burning your token usage - here's the data" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Our research across C++, Java, and Python shows that agents working on&lt;span style="font-weight: bold;"&gt; unhealthy codebases consume up to 50% more tokens to complete the same tasks&lt;/span&gt;. That’s in addition to the increased defect risk covered in &lt;a href="https://codescene.com/hubfs/whitepapers/AI-Ready-Code-How-Code-Health-Determines-AI-Performance.pdf"&gt;earlier research&lt;/a&gt;. You're not just getting worse output. You're paying significantly more for it.&lt;/p&gt; 
&lt;p&gt;Knowing that your unhealthy code burns excess tokens is useful. Having a workflow that prevents it from getting worse with every agent commit is what changes the outcome.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/unhealthy-code-is-burning-your-token-usage-heres-the-data" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/token_waste_1200x600.png" alt="Unhealthy code is burning your token usage - here's the data" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Our research across C++, Java, and Python shows that agents working on&lt;span style="font-weight: bold;"&gt; unhealthy codebases consume up to 50% more tokens to complete the same tasks&lt;/span&gt;. That’s in addition to the increased defect risk covered in &lt;a href="https://codescene.com/hubfs/whitepapers/AI-Ready-Code-How-Code-Health-Determines-AI-Performance.pdf"&gt;earlier research&lt;/a&gt;. You're not just getting worse output. You're paying significantly more for it.&lt;/p&gt; 
&lt;p&gt;Knowing that your unhealthy code burns excess tokens is useful. Having a workflow that prevents it from getting worse with every agent commit is what changes the outcome.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Funhealthy-code-is-burning-your-token-usage-heres-the-data&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Code Quality</category>
      <category>AI Coding</category>
      <pubDate>Thu, 28 May 2026 16:14:00 GMT</pubDate>
      <guid>https://codescene.com/blog/unhealthy-code-is-burning-your-token-usage-heres-the-data</guid>
      <dc:date>2026-05-28T16:14:00Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
    <item>
      <title>Making Legacy Code AI-Ready: Benchmarks on Agentic Refactoring</title>
      <link>https://codescene.com/blog/making-legacy-code-ai-ready-benchmarks-on-agentic-refactoring</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/making-legacy-code-ai-ready-benchmarks-on-agentic-refactoring" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/Making%20Legacy%20Code%20AI-Ready%20Benchmarks%20on%20Agentic%20Refactoring_600x350_1.png" alt="Making Legacy Code AI-Ready: Benchmarks on Agentic Refactoring" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Most enterprises are now on a trajectory towards agentic AI. The general assumption is that faster coding will translate into increased productivity across the board.&lt;br&gt;&lt;br&gt;However, there’s a potential clash between expectations and reality:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt; &lt;p&gt;The &lt;a href="https://codescene.com/blog/benchmarking-code-health-refactoring-roi"&gt;Code Health benchmarks&lt;/a&gt; show that the average Hotspot Code Health in the IT sector is 5.15 on a 10.0 scale.&lt;/p&gt; &lt;/li&gt; 
 &lt;li&gt; &lt;p&gt;The threshold for healthy code that is easy for a human to understand is 9.0.&lt;/p&gt; &lt;/li&gt; 
 &lt;li&gt; &lt;p&gt;AI requires even better code quality, not less: &lt;a href="https://codescene.com/hubfs/whitepapers/AI-Ready-Code-How-Code-Health-Determines-AI-Performance.pdf"&gt;research on AI-friendly code&lt;/a&gt; shows that you need at least 9.4 to keep AI-induced bugs in check.&lt;/p&gt; &lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Given that the average industry Code Health is only 5.15, naive AI adoption is unlikely to deliver the expected benefits. Not because the agent’s underlying LLMs are weak, but because the average code structure is too unhealthy for an AI to comprehend and safely modify.&lt;/p&gt; 
&lt;p&gt;This implies that legacy code is a key bottleneck for enterprise adoption of agentic coding tools. Before AI can accelerate feature work, code health needs to improve. Let’s explore how AI can guide that uplift.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/making-legacy-code-ai-ready-benchmarks-on-agentic-refactoring" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/Making%20Legacy%20Code%20AI-Ready%20Benchmarks%20on%20Agentic%20Refactoring_600x350_1.png" alt="Making Legacy Code AI-Ready: Benchmarks on Agentic Refactoring" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Most enterprises are now on a trajectory towards agentic AI. The general assumption is that faster coding will translate into increased productivity across the board.&lt;br&gt;&lt;br&gt;However, there’s a potential clash between expectations and reality:&lt;/p&gt; 
&lt;ul&gt; 
 &lt;li&gt; &lt;p&gt;The &lt;a href="https://codescene.com/blog/benchmarking-code-health-refactoring-roi"&gt;Code Health benchmarks&lt;/a&gt; show that the average Hotspot Code Health in the IT sector is 5.15 on a 10.0 scale.&lt;/p&gt; &lt;/li&gt; 
 &lt;li&gt; &lt;p&gt;The threshold for healthy code that is easy for a human to understand is 9.0.&lt;/p&gt; &lt;/li&gt; 
 &lt;li&gt; &lt;p&gt;AI requires even better code quality, not less: &lt;a href="https://codescene.com/hubfs/whitepapers/AI-Ready-Code-How-Code-Health-Determines-AI-Performance.pdf"&gt;research on AI-friendly code&lt;/a&gt; shows that you need at least 9.4 to keep AI-induced bugs in check.&lt;/p&gt; &lt;/li&gt; 
&lt;/ul&gt; 
&lt;p&gt;Given that the average industry Code Health is only 5.15, naive AI adoption is unlikely to deliver the expected benefits. Not because the agent’s underlying LLMs are weak, but because the average code structure is too unhealthy for an AI to comprehend and safely modify.&lt;/p&gt; 
&lt;p&gt;This implies that legacy code is a key bottleneck for enterprise adoption of agentic coding tools. Before AI can accelerate feature work, code health needs to improve. Let’s explore how AI can guide that uplift.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Fmaking-legacy-code-ai-ready-benchmarks-on-agentic-refactoring&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Code Quality</category>
      <pubDate>Wed, 18 Mar 2026 15:53:36 GMT</pubDate>
      <guid>https://codescene.com/blog/making-legacy-code-ai-ready-benchmarks-on-agentic-refactoring</guid>
      <dc:date>2026-03-18T15:53:36Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
    <item>
      <title>Agentic AI Coding: Best Practice Patterns for Speed with Quality</title>
      <link>https://codescene.com/blog/agentic-ai-coding-best-practice-patterns-for-speed-with-quality</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/agentic-ai-coding-best-practice-patterns-for-speed-with-quality" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/AI-Friendly-Code_Chart.png" alt="Agentic AI Coding: Best Practice Patterns for Speed with Quality" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;This year has marked an interesting and fundamental shift. I’ve been coding for almost 40 years, 30 of those professionally, and yet I’m now at a point where 100% of my production code is written and maintained by AI agents. I’m not alone: companies at the forefront of the agentic AI revolution report the same pattern.&lt;/p&gt; 
&lt;p&gt;But let’s not get carried away by hype. This shift didn’t come for free. Coding via agents requires more rigor, more structure, more code quality, not less.&lt;/p&gt; 
&lt;p&gt;In this article I’ll share what worked for my team, as well as the general patterns I’ve observed in the industry. (I’m in the fortunate situation of regularly meeting and working with organizations across the globe in all states of AI adoption).&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/agentic-ai-coding-best-practice-patterns-for-speed-with-quality" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/AI-Friendly-Code_Chart.png" alt="Agentic AI Coding: Best Practice Patterns for Speed with Quality" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;This year has marked an interesting and fundamental shift. I’ve been coding for almost 40 years, 30 of those professionally, and yet I’m now at a point where 100% of my production code is written and maintained by AI agents. I’m not alone: companies at the forefront of the agentic AI revolution report the same pattern.&lt;/p&gt; 
&lt;p&gt;But let’s not get carried away by hype. This shift didn’t come for free. Coding via agents requires more rigor, more structure, more code quality, not less.&lt;/p&gt; 
&lt;p&gt;In this article I’ll share what worked for my team, as well as the general patterns I’ve observed in the industry. (I’m in the fortunate situation of regularly meeting and working with organizations across the globe in all states of AI adoption).&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Fagentic-ai-coding-best-practice-patterns-for-speed-with-quality&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Code Quality</category>
      <pubDate>Fri, 20 Feb 2026 12:28:33 GMT</pubDate>
      <guid>https://codescene.com/blog/agentic-ai-coding-best-practice-patterns-for-speed-with-quality</guid>
      <dc:date>2026-02-20T12:28:33Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
    <item>
      <title>Strengthening the Inner Developer Loop: Turn AI Into a Reliable Engineering Partner</title>
      <link>https://codescene.com/blog/strengthening-the-inner-developer-loop-turn-ai-into-a-reliable-engineering-partner</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/strengthening-the-inner-developer-loop-turn-ai-into-a-reliable-engineering-partner" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/inner-feedback-loop-automated-code-quality-for-ai-agents-and-developers.png" alt="Inner feedback loop - framework for deploying AI-generated code that is maintainable" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;What if AI could accelerate development without leaving a trail of complexity, defects, and hard-to-reason-about code that even your own AI agents fail to understand?&lt;/p&gt; 
&lt;p&gt;That’s the promise of a well-designed inner developer loop: a feedback system that keeps AI productive and predictable. In this article, we present a practical and research-backed framework for building codebases that stay understandable to both humans and machines, today and for the years to come.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/strengthening-the-inner-developer-loop-turn-ai-into-a-reliable-engineering-partner" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/inner-feedback-loop-automated-code-quality-for-ai-agents-and-developers.png" alt="Inner feedback loop - framework for deploying AI-generated code that is maintainable" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;What if AI could accelerate development without leaving a trail of complexity, defects, and hard-to-reason-about code that even your own AI agents fail to understand?&lt;/p&gt; 
&lt;p&gt;That’s the promise of a well-designed inner developer loop: a feedback system that keeps AI productive and predictable. In this article, we present a practical and research-backed framework for building codebases that stay understandable to both humans and machines, today and for the years to come.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Fstrengthening-the-inner-developer-loop-turn-ai-into-a-reliable-engineering-partner&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Code Quality</category>
      <pubDate>Tue, 02 Dec 2025 13:30:47 GMT</pubDate>
      <guid>https://codescene.com/blog/strengthening-the-inner-developer-loop-turn-ai-into-a-reliable-engineering-partner</guid>
      <dc:date>2025-12-02T13:30:47Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
    <item>
      <title>Human, What Must I Tell You?</title>
      <link>https://codescene.com/blog/human-what-must-i-tell-you</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/human-what-must-i-tell-you" title="" class="hs-featured-image-link"&gt; &lt;img src="https://i0.wp.com/mrksbrg.com/wp-content/uploads/2023/05/chatgpt_ver2.jpg?resize=681%2C1024" alt="Human, What Must I Tell You?" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/human-what-must-i-tell-you" title="" class="hs-featured-image-link"&gt; &lt;img src="https://i0.wp.com/mrksbrg.com/wp-content/uploads/2023/05/chatgpt_ver2.jpg?resize=681%2C1024" alt="Human, What Must I Tell You?" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;   
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Fhuman-what-must-i-tell-you&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Research</category>
      <pubDate>Tue, 23 Sep 2025 13:48:42 GMT</pubDate>
      <guid>https://codescene.com/blog/human-what-must-i-tell-you</guid>
      <dc:date>2025-09-23T13:48:42Z</dc:date>
      <dc:creator>Markus Borg</dc:creator>
    </item>
    <item>
      <title>Requirements on Technical Debt: Dare to Specify Them!</title>
      <link>https://codescene.com/blog/requirements-on-technical-debt-dare-to-specify-them</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/requirements-on-technical-debt-dare-to-specify-them" title="" class="hs-featured-image-link"&gt; &lt;img src="https://i0.wp.com/mrksbrg.com/wp-content/uploads/2023/02/codescene.png?resize=723%2C541" alt="Requirements on Technical Debt: Dare to Specify Them!" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/requirements-on-technical-debt-dare-to-specify-them" title="" class="hs-featured-image-link"&gt; &lt;img src="https://i0.wp.com/mrksbrg.com/wp-content/uploads/2023/02/codescene.png?resize=723%2C541" alt="Requirements on Technical Debt: Dare to Specify Them!" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Frequirements-on-technical-debt-dare-to-specify-them&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Research</category>
      <pubDate>Tue, 23 Sep 2025 13:48:25 GMT</pubDate>
      <guid>https://codescene.com/blog/requirements-on-technical-debt-dare-to-specify-them</guid>
      <dc:date>2025-09-23T13:48:25Z</dc:date>
      <dc:creator>Markus Borg</dc:creator>
    </item>
    <item>
      <title>Requirements for Organizational Resilience: Engineering Developer Happiness</title>
      <link>https://codescene.com/blog/requirements-for-organizational-resilience-engineering-developer-happiness</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/requirements-for-organizational-resilience-engineering-developer-happiness" title="" class="hs-featured-image-link"&gt; &lt;img src="https://i0.wp.com/mrksbrg.com/wp-content/uploads/2024/06/vicious_cycle.png?resize=458%2C275" alt="Requirements for Organizational Resilience: Engineering Developer Happiness" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/requirements-for-organizational-resilience-engineering-developer-happiness" title="" class="hs-featured-image-link"&gt; &lt;img src="https://i0.wp.com/mrksbrg.com/wp-content/uploads/2024/06/vicious_cycle.png?resize=458%2C275" alt="Requirements for Organizational Resilience: Engineering Developer Happiness" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Frequirements-for-organizational-resilience-engineering-developer-happiness&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Research</category>
      <pubDate>Tue, 23 Sep 2025 13:47:17 GMT</pubDate>
      <guid>https://codescene.com/blog/requirements-for-organizational-resilience-engineering-developer-happiness</guid>
      <dc:date>2025-09-23T13:47:17Z</dc:date>
      <dc:creator>Markus Borg</dc:creator>
    </item>
    <item>
      <title>Cyclomatic complexity - a fresh look at code complexity｜Blog</title>
      <link>https://codescene.com/blog/bumpy-road-code-complexity-in-context/</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/bumpy-road-code-complexity-in-context/" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/Cyclomatic%20complexity%20really%20doesnt%20tell%20much%20about%20the%20effort%20to%20understand%20a%20piece%20of%20code..svg" alt="Cyclomatic complexity - a fresh look at code complexity｜Blog" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;Complex code slows down development productivity, increases the delivery risk, and leads to excess maintenance costs.&lt;/span&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/bumpy-road-code-complexity-in-context/" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hubfs/Cyclomatic%20complexity%20really%20doesnt%20tell%20much%20about%20the%20effort%20to%20understand%20a%20piece%20of%20code..svg" alt="Cyclomatic complexity - a fresh look at code complexity｜Blog" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;Complex code slows down development productivity, increases the delivery risk, and leads to excess maintenance costs.&lt;/span&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Fbumpy-road-code-complexity-in-context%2F&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Mon, 22 Sep 2025 14:45:59 GMT</pubDate>
      <guid>https://codescene.com/blog/bumpy-road-code-complexity-in-context/</guid>
      <dc:date>2025-09-22T14:45:59Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
    <item>
      <title>Architectural Analysis Simplified and growing Programming Language support</title>
      <link>https://codescene.com/blog/architectural-analysis-simplified-and-growing-programming-language-support</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/architectural-analysis-simplified-and-growing-programming-language-support" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hs-fs/hubfs/Featured%20image%20-%20Architectural.png?width=2399&amp;amp;quality=high" alt="Graphs showing how CodeScene auto-generates your architectural definitions so that you can analyse hotspots, coupling, and knowledge distribution on a system level." class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;We’re proud to announce a new release of&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #377e90;"&gt;&lt;a href="http://empear-7007026.hs-sites.com/pricing" style="color: #377e90;"&gt;CodeScene on-prem&lt;/a&gt;&lt;/span&gt;, version 4.2.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://codescene.com/blog/architectural-analysis-simplified-and-growing-programming-language-support" title="" class="hs-featured-image-link"&gt; &lt;img src="https://codescene.com/hs-fs/hubfs/Featured%20image%20-%20Architectural.png?width=2399&amp;amp;quality=high" alt="Graphs showing how CodeScene auto-generates your architectural definitions so that you can analyse hotspots, coupling, and knowledge distribution on a system level." class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;We’re proud to announce a new release of&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: #377e90;"&gt;&lt;a href="http://empear-7007026.hs-sites.com/pricing" style="color: #377e90;"&gt;CodeScene on-prem&lt;/a&gt;&lt;/span&gt;, version 4.2.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=7007026&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fcodescene.com%2Fblog%2Farchitectural-analysis-simplified-and-growing-programming-language-support&amp;amp;bu=https%253A%252F%252Fcodescene.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Product</category>
      <pubDate>Mon, 22 Sep 2025 12:12:25 GMT</pubDate>
      <guid>https://codescene.com/blog/architectural-analysis-simplified-and-growing-programming-language-support</guid>
      <dc:date>2025-09-22T12:12:25Z</dc:date>
      <dc:creator>Adam Tornhill</dc:creator>
    </item>
  </channel>
</rss>
