Learn Enough Command Line to Be Dangerous (Draft)

When introducing kill, don't use -9. Not a good way for a beginner to learn kill. Guess you weren't kidding with "Learn Enough Command Line to Be Dangerous". Understood that it's a draft. Coming together nicely.

Nicely done! Feedback, since it&#x27;s a draft: There&#x27;s a lot of introductory verbiage at the beginning. I wonder if this could be condensed or put off in a sidebar.<p>On OS X, for some languages at least, if the user has installed additional keyboard input languages, then Command-space may be taken over for switching input language, and thus the instructions for opening a terminal with Spotlight would not work.<p>Looked through some of the explanations and things such as the walkthrough of Ctrl-C are very well done for true beginner level readers.

What a great tutorial. This was definitely an underserved portion of the learning process. Also, learned `cd -` and I think my days will be ever so slightly but definitely better for it. Thanks for sharing!<p>Also definitely go into why `rm -rf` is such a dangerous command, by that stage in the tutorial the reader has likely begun feeling confident experimenting but has yet to encounter anything really dangerous.

The point in the introduction about people who work <i>with</i> developers needing to be familiar with the console is hugely important, in my opinion. It&#x27;s the one bridge, short of someone having actual previous coding experience, that really makes my life easier at work. It also makes people feel, or so I observe, more confident and in control of their workstation.

I really like the format and styling! It&#x27;s broken up nicely with the images you added and the commands are kept to the really important ones. The summaries at the end of each chapter is great as takeaway. Maybe you could create a cheat sheet of the combination of summaries?<p>I&#x27;m looking forward to the Git edition of this series.

For people who would like to go further, and explore writing command line tools (instead of only using them), in C [1], for Linux [2], this post and the linked article in it, by me, may be of help:<p>Developing a Linux command-line utility:<p><a href="http:&#x2F;&#x2F;jugad2.blogspot.in&#x2F;2014&#x2F;09&#x2F;my-ibm-developerworks-article.html" rel="nofollow">http:&#x2F;&#x2F;jugad2.blogspot.in&#x2F;2014&#x2F;09&#x2F;my-ibm-developerworks-arti...</a><p>[1] In C, but the utility development guidelines described in the article mostly apply to other languages like Python and Ruby too, since the main principles are the same.<p>[2] It may compile and run on Mac OS X too, since it is a Unix, but I haven&#x27;t tested it on that platform.

Under &#x27;less&#x27; commands - can suggest &#x27;g&#x27; instead of &#x27;1G&#x27;.

I really wish developers today (in the 2000s, for Christ&#x27;s sake) didn&#x27;t have to deal with such a horrible UI.<p>The Unix Hater&#x27;s Hanbook says it well: &quot;The original Unix solved a problem and solved it well, as did the Roman numeral system, the mercury treatment for syphilis, and carbon paper. And like those technologies, Unix, too, rightfully belongs to history. It was developed for a machine with little memory, tiny disks, no graphics, no networking, and no power.&quot;<p>Bu since wee seem to be stuck with Unix, I guess we need any guidance we can get.

Why is 1,060 KB of JavaScript required to display this wonderful text page? Is there a way to read just the text without any interactive elements?

What has the world come to where the command line is something foreign to a software developer? Throw me on an island with a few unprovisioned *inux boxes and I&#x27;m all set.

I understand this thing is aimed to create super power perception within tech novice ppl when some command line is learned, but, seriously, this new fashion of claiming that if you wrote couple lines of code means you are software guru now, is absurd.

What do you have to do to get at the content?

Commandline.fu is a good source too