<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Lean Team blog</title>
<link>https://www.leanteamproducts.com/blog</link>
<atom:link href="https://www.leanteamproducts.com/rss.xml" rel="self" type="application/rss+xml"/>
<description>Practical notes for software teams: AI coding agents, logging costs and fast, reliable tests.</description>
<language>en</language>
<item>
<title>5 mistakes AI coding agents make, and how to catch them before merge</title>
<link>https://www.leanteamproducts.com/blog/ai-code-review-mistakes</link>
<guid isPermaLink="true">https://www.leanteamproducts.com/blog/ai-code-review-mistakes</guid>
<pubDate>Fri, 20 Nov 2026 14:00:00 GMT</pubDate>
<description>AI coding agents write code fast and repeat the same handful of mistakes. A checklist for reviewing AI-assisted diffs, plus the one question to ask before merging.</description>
<category>ai</category><category>codereview</category><category>programming</category><category>productivity</category>
</item>
<item>
<title>Flaky tests: a triage rule that actually gets them fixed</title>
<link>https://www.leanteamproducts.com/blog/flaky-test-triage</link>
<guid isPermaLink="true">https://www.leanteamproducts.com/blog/flaky-test-triage</guid>
<pubDate>Fri, 20 Nov 2026 14:00:00 GMT</pubDate>
<description>Every flaky test teaches the team to ignore red builds. A four-step rule for quarantining and fixing them, and a table of the usual causes with their fixes.</description>
<category>testing</category><category>ci</category><category>devops</category><category>programming</category>
</item>
<item>
<title>One stack trace, 40 billed log entries: the logging cost most teams miss</title>
<link>https://www.leanteamproducts.com/blog/stack-traces-logging-cost</link>
<guid isPermaLink="true">https://www.leanteamproducts.com/blog/stack-traces-logging-cost</guid>
<pubDate>Fri, 20 Nov 2026 14:00:00 GMT</pubDate>
<description>Most log platforms bill each line of a stack trace as its own entry. How to spot it, and two ways to fix it: structured logging, or joining lines in the collector.</description>
<category>devops</category><category>logging</category><category>cloud</category><category>sre</category>
</item>
</channel>
</rss>
