<story><title>When deployments are easy, code becomes simpler</title><url>https://bitbytebit.substack.com/p/when-deployments-are-easy-code-becomes</url></story><parent_chain><item><author>smokel</author><text>I have recently seen someone wrap a single function in about 10 classes of Java to turn it into a standalone application, slap on some Docker Compose magic, add some build scripts, and then continue to look proud at the feature being wholly configurable at deployment time.&lt;p&gt;Of course, the deployment team would have to be informed about this change, so some documentation was required as well, but that was exactly the part of the process where most effort was saved.&lt;p&gt;Note that all this was used for a system that would be deployed only at one customer, and the feature would always be on.  Yes, a boolean flag would have been a better solution for this.&lt;p&gt;My cynicism is probably not the best approach to change the world for the better, so any hint on how to teach younger colleagues to stop snacking micro service candy is much appreciated.</text></item></parent_chain><comment><author>drekipus</author><text>Just raise it up early, often, and simply.&lt;p&gt;&amp;quot;Isn&amp;#x27;t this just a Boolean flag? If X else y?&amp;quot;&lt;p&gt;I&amp;#x27;ve saved a great many man months by doing just this. Sometimes work just vanishes. And it&amp;#x27;s not just the juniors that do it, sometimes the senior &amp;#x2F; tech lead types just miss a crucial point to make the solution trivial.&lt;p&gt;But juniors are often used to wanting to make work, rather than solve a problem.</text></comment>
<story><title>When deployments are easy, code becomes simpler</title><url>https://bitbytebit.substack.com/p/when-deployments-are-easy-code-becomes</url></story><parent_chain><item><author>smokel</author><text>I have recently seen someone wrap a single function in about 10 classes of Java to turn it into a standalone application, slap on some Docker Compose magic, add some build scripts, and then continue to look proud at the feature being wholly configurable at deployment time.&lt;p&gt;Of course, the deployment team would have to be informed about this change, so some documentation was required as well, but that was exactly the part of the process where most effort was saved.&lt;p&gt;Note that all this was used for a system that would be deployed only at one customer, and the feature would always be on.  Yes, a boolean flag would have been a better solution for this.&lt;p&gt;My cynicism is probably not the best approach to change the world for the better, so any hint on how to teach younger colleagues to stop snacking micro service candy is much appreciated.</text></item></parent_chain><comment><author>digging</author><text>&amp;gt; My cynicism is probably not the best approach to change the world for the better, so any hint on how to teach younger colleagues to stop snacking micro service candy is much appreciated.&lt;p&gt;I could be way off base here, but I&amp;#x27;d bet a lot of junior devs are just trying to stand out. They want respect, raises, promotions, and new job offers. Invisible good solutions don&amp;#x27;t bring those.</text></comment>