In what way?<p>My general advice is to do things you&#x27;ve done before, but move them to Unix. For example, if you&#x27;re on Mac OS X, use pbcopy and pbpaste, which read from&#x2F;into stdout and stdin, respectively, rather than doing Cmd-C and Cmd-V. Use pipes gradually, one or two at a time, and then you start to see how it can fit into a bigger workflow.<p>If you work with data, it&#x27;s even easier to find ways to practice pipes. Here&#x27;s a gist showing how to use pipes with other Unix utils and SQLite to do a quick command-line analysis of SF restaurant inspections (namely, finding dirty Starbucks:<p><a href="https:&#x2F;&#x2F;gist.github.com&#x2F;dannguyen&#x2F;c9dd7afc4300ae8715d8" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;dannguyen&#x2F;c9dd7afc4300ae8715d8</a><p>It&#x27;s actually a bit convoluted, as it focuses on using SQLite. You could do a similar analysis just using the excellent csvkit tool to slice and dice CSV files via the command-line.<p>I put together a list of Unix tools that I liked for a class that used a lot of piping: <a href="http:&#x2F;&#x2F;www.compciv.org&#x2F;unix-tools&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.compciv.org&#x2F;unix-tools&#x2F;</a>