<p>I may eventually just dedicate this thing to the public domain, but for the
time being please feel free to use it under the terms of Creative Commons BY-SA
(Attribution / Share-Alike), whatever the latest version is. I promise I will
not license it under more restrictive terms than that.</p>
<hr/>
<h1><aname=the-command-line-as-a-literary-environmenthref=#the-command-line-as-a-literary-environment>#</a> 1. the command line as a literary environment</h1>
@ -1684,11 +1683,13 @@ and mark the interesting ones.</p>
<em>write</em> them. I write little tiny ones all the time, and the ability to read
other people’s scripts comes in handy. Oftentimes, the best, most tasteful way
to automate something is to build a script out of the commonly available
commands. They’re already there on millions of machines. Many of them have
been pretty well understood for a generation, and most of them will probably be
around for a generation or three to come. They do neat stuff. Scripts let you
build on the things you’ve already figured out on the command line, and give
repeatable operations a memorable, user-friendly name.</p>
commands. The standard tools are already there on millions of machines. Many
of them have been pretty well understood for a generation, and most of them
will probably be around for a generation or three to come. They do neat stuff.
Scripts let you build on things you’ve already figured out, and give repeatable
operations a memorable, user-friendly name. They encourage reuse of existing
programs, and help express your ideas in a repeatable fashion to people who’ll
come after you.</p>
<p>One of the reliable markers of powerful software is that it can be scripted: It
extends to its users some of the same power that its authors used in creating
@ -1751,11 +1752,21 @@ out that these work just about as well for English text as they do for code.</p>
<hr/>
<h1><aname=further-readinghref=#further-reading>#</a> further reading</h1>
<h1><aname=further-readinghref=#further-reading>#</a> 7. further reading</h1>
<ul>
<li><em>The Unix Programming Environment</em> - Brian W. Kernighan, Rob Pike</li>
</ul>
<hr/>
<h1><aname=noteshref=#notes>#</a> notes</h1>
<p><em>The Unix Programming Environment</em> - Brian W. Kernighan, Rob Pike</p>
<p>For now, this section is a catch-all for things that don’t quite fit anywhere
else, but might become end-notes, sidebars, or some other kind of marginalia.</p>
<h2><aname=bits-that-might-become-end-notes-laterhref=#bits-that-might-become-end-notes-later>#</a> bits that might become end notes later</h2>
<pstyle="text-align:center;"> *</p>
<p>I just ran <code>dict model</code>. It’s a word with many fascinating definitions, but my
favorite of the bunch is probably this bit of ridiculous, eye-glazing