<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nicoburns</author><text>&amp;gt; All of these replacement commands dry run by default&lt;p&gt;Same here. In addition if there&amp;#x27;s never a use case for running in production (e.g. at one point we had a command that reset a dev environment to a clean slate) then the command will actually specifically check for the production environment and refuse to run as an extra failsafe.</text><parent_chain><item><author>overshard</author><text>At my work I&amp;#x27;ve gone through and setup a variety of &amp;quot;replacement&amp;quot; commands for commands that may have dire impact on production systems. All of these replacement commands dry run by default (or fake dry run&amp;#x2F;try to create a dry run the best they can) and require a &amp;quot;--do-it&amp;quot; (think emperor palpatine voice) flag to do the intended operation. I&amp;#x27;ve had multiple coworkers thank me for this setup as it&amp;#x27;s saved people from silly typos and mistakes, one such being the different handling of programs in the use of and ending &amp;quot;&amp;#x2F;&amp;quot; in folders. ex. &amp;quot;&amp;#x2F;etc&amp;quot; is different than &amp;quot;&amp;#x2F;etc&amp;#x2F;&amp;quot; sometimes for certain operations.&lt;p&gt;I&amp;#x27;d like to one day see a global flag on operating systems to dry run nearly all commands that changed anything.</text></item></parent_chain></comment><story><title>In praise of --dry-run</title><url>https://www.gresearch.co.uk/article/in-praise-of-dry-run/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Twirrim</author><text>I&amp;#x27;ve largely switched to writing all my tools dry-run by default.  We&amp;#x27;ve had a few undesirable events from tools that had --dry-run modes and accidentally got run without.  Making --run or similar necessary almost guarantees it&amp;#x27;s never run without intention.</text><parent_chain><item><author>overshard</author><text>At my work I&amp;#x27;ve gone through and setup a variety of &amp;quot;replacement&amp;quot; commands for commands that may have dire impact on production systems. All of these replacement commands dry run by default (or fake dry run&amp;#x2F;try to create a dry run the best they can) and require a &amp;quot;--do-it&amp;quot; (think emperor palpatine voice) flag to do the intended operation. I&amp;#x27;ve had multiple coworkers thank me for this setup as it&amp;#x27;s saved people from silly typos and mistakes, one such being the different handling of programs in the use of and ending &amp;quot;&amp;#x2F;&amp;quot; in folders. ex. &amp;quot;&amp;#x2F;etc&amp;quot; is different than &amp;quot;&amp;#x2F;etc&amp;#x2F;&amp;quot; sometimes for certain operations.&lt;p&gt;I&amp;#x27;d like to one day see a global flag on operating systems to dry run nearly all commands that changed anything.</text></item></parent_chain></comment><story><title>In praise of --dry-run</title><url>https://www.gresearch.co.uk/article/in-praise-of-dry-run/</url></story>