<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flaky-Tests on F. Latini - IT Engineer</title><link>https://latini.dev/tags/flaky-tests/</link><description>Recent content in Flaky-Tests on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 29 Oct 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/flaky-tests/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Build Is Slow Because Everyone Owns It</title><link>https://latini.dev/posts/your-build-is-slow-because-everyone-owns-it/</link><pubDate>Thu, 29 Oct 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/your-build-is-slow-because-everyone-owns-it/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Nobody decides to have a twenty-five-minute build. It gets there one reasonable step at a time: a new scanner here, an integration suite there, a cache that quietly stopped hitting, a runner pool sized to last year&amp;rsquo;s headcount. Every team owns a step, so nobody owns the total, and the total is the only number developers experience. Flaky tests finish the job by teaching everyone that red means &amp;ldquo;press retry&amp;rdquo;, which is the moment the pipeline stops being a signal. The fix is not a quarterly &amp;ldquo;speed up CI&amp;rdquo; sprint. It is treating feedback-loop latency as a platform capability with an owner: a published time budget for push-to-signal, caching and test selection as shared primitives rather than per-repo heroics, runners sized on queue time rather than on the invoice, and flaky tests quarantined with an owner and an expiry date. Measure the wait the developer actually sits through, not the average job duration on a dashboard.&lt;/p&gt;</description></item></channel></rss>