<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>amalgamated_inc</author><text>I think that you probably have 80% of the gross capability, but you will gain a huge level of refinement. I&amp;#x27;m about 10-15 years into the command line (depending on how you count, lol) and I keep finding more stuff that just wouldn&amp;#x27;t stick 5 years ago, because I simply didn&amp;#x27;t have those problems yet.&lt;p&gt;E.g. there was a time in my life when I didn&amp;#x27;t get what `xargs` even did, I literally couldn&amp;#x27;t grok it. Now, I can&amp;#x27;t imagine life without `-0`!&lt;p&gt;The composability of UNIX commands is just so amazing. Every command builds on every other command. I haven&amp;#x27;t seen that with any other tools or program.</text><parent_chain><item><author>velavar</author><text>Do you think that this is because they don&amp;#x27;t really need to anymore with all the nice GUI&amp;#x2F;tools around? Is there an advantage to bring able to do something on a command line vs other ways?&lt;p&gt;Asking because I&amp;#x27;m at a bit of a crossroads - I have a good handle on about 5% of the command line knowledge which gets me through 80% of the stuff I need to do. I&amp;#x27;m wondering if learning to use more commands is worth the effort when I can already get the task done without using the command line?</text></item><item><author>channel_t</author><text>I consider this book pretty much required reading for junior devs and others in engineering who don&amp;#x27;t have a decent handle on basic Unix skills for whatever reason--which seems to be a more common occurrence these days than earlier in my career.</text></item></parent_chain></comment><story><title>The Linux Command Line</title><url>https://www.linuxcommand.org/tlcl.php</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>gofreddygo</author><text>more commands are a side effect of more capability.&lt;p&gt;If you get a sense of things you can do with (|, &amp;amp; , &amp;gt;) and a dozen or so commands like&lt;p&gt;sort | uniq | cut | paste | join | head | tail | sed | awk | wc | tr | fmt | col | nl | pr | find | grep | tar | export&lt;p&gt;The value you get in return is intense for the effort invested.&lt;p&gt;Plus, in the 10 years i&amp;#x27;ve been maintaining code, bash scripts are the minority that still work as they used to with almost no change needed.&lt;p&gt;That single handedly is worth my money.</text><parent_chain><item><author>velavar</author><text>Do you think that this is because they don&amp;#x27;t really need to anymore with all the nice GUI&amp;#x2F;tools around? Is there an advantage to bring able to do something on a command line vs other ways?&lt;p&gt;Asking because I&amp;#x27;m at a bit of a crossroads - I have a good handle on about 5% of the command line knowledge which gets me through 80% of the stuff I need to do. I&amp;#x27;m wondering if learning to use more commands is worth the effort when I can already get the task done without using the command line?</text></item><item><author>channel_t</author><text>I consider this book pretty much required reading for junior devs and others in engineering who don&amp;#x27;t have a decent handle on basic Unix skills for whatever reason--which seems to be a more common occurrence these days than earlier in my career.</text></item></parent_chain></comment><story><title>The Linux Command Line</title><url>https://www.linuxcommand.org/tlcl.php</url></story>