<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code on Vegatron 🌈✨</title><link>https://vegatron.engineering/tags/code/</link><description>Recent content in Code on Vegatron 🌈✨</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 04 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vegatron.engineering/tags/code/index.xml" rel="self" type="application/rss+xml"/><item><title>Code Freeze</title><link>https://vegatron.engineering/posts/code-freeze/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate><guid>https://vegatron.engineering/posts/code-freeze/</guid><description>&lt;p>Your reactive code freeze is trying to tell you something; you should listen.&lt;/p>
&lt;h2 id="latent-risk">Latent risk&lt;/h2>
&lt;p>A reactive code freeze is a sign that you risk breaking something.
Or of causing damage at the worst possible time.&lt;/p>
&lt;p>Many teams just shrug it off as the cost of continuous delivery ¯\_(ツ)_/¯&lt;/p>
&lt;p>Just piling up changes ready for the green light is not helpful.
Worse still if the freeze extends for many days or weeks.&lt;/p></description></item></channel></rss>