<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on Server Noise</title><link>https://sn.noisycall.com/tags/engineering/</link><description>Recent content in Engineering on Server Noise</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 May 2026 18:05:31 +0530</lastBuildDate><atom:link href="https://sn.noisycall.com/tags/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Feature Branches - a Tiny Experiment</title><link>https://sn.noisycall.com/posts/feature-branches---a-tiny-experiment/</link><pubDate>Sun, 24 May 2026 18:05:31 +0530</pubDate><guid>https://sn.noisycall.com/posts/feature-branches---a-tiny-experiment/</guid><description>&lt;p&gt;At my current workplace (at the time of writing), we have what could be best described as the classic &amp;ldquo;trunk based&amp;rdquo; development pattern.&lt;/p&gt;
&lt;p&gt;A branch called main, with release branches cut off from it at arbitrary points. Work merged in whenever it was ready. You get the idea, but if not, &lt;a href="https://trunkbaseddevelopment.com/"&gt;this seems to be a good illustration&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This works pretty well and is ultimately what will continue to be used by us for days to come. However, I had a specific set of problems with this method, that I aimed to solve using pretty specific approach, that builds on top of trunks, and is the namesake of this post.&lt;/p&gt;</description></item></channel></rss>