<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Bruce on AI Engineering</title><link>http://www.heyuan110.com/tags/testing/</link><description>Recent content in Testing on Bruce on AI Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 31 Jan 2026 09:10:00 +0800</lastBuildDate><atom:link href="http://www.heyuan110.com/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>High-Frequency Commits: Engineering Practices for 100+ Commits per Day</title><link>http://www.heyuan110.com/posts/ai/2026-01-31-high-frequency-commits-strategy/</link><pubDate>Sat, 31 Jan 2026 09:10:00 +0800</pubDate><guid>http://www.heyuan110.com/posts/ai/2026-01-31-high-frequency-commits-strategy/</guid><description>&lt;p&gt;&lt;img src="http://www.heyuan110.com/posts/ai/2026-01-31-high-frequency-commits-strategy/cover.webp"
 alt="Engineering practices for high-frequency commits and stable delivery"
 
 loading="lazy"
 decoding="async"
 fetchpriority="low"
 width="1200"
 height="630"
/&gt;
&lt;/p&gt;
&lt;p&gt;With AI coding tools accelerating development speed, many teams are hitting a new normal: &lt;strong&gt;dozens to hundreds of commits per day&lt;/strong&gt;. The question becomes sharp: why do some projects get faster while others spiral into chaos?&lt;/p&gt;
&lt;p&gt;This article does not argue whether you should slow down. Instead, it focuses on the engineering system: &lt;strong&gt;when commit frequency skyrockets, how do you keep your product under control?&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>