Problem solving with Unix commands
Gary Bernhardt[1] gave a great talk about practical problem solving with the unix shell: &quot;The Unix Chainsaw&quot;[2].<p>&quot;Half-assed is OK when you only need half of an ass.&quot;<p>In the talk, he gives several demonstrations a key aspect of <i>why</i> unix pipelines are so practically useful: you build them <i>interactively</i>. A complicated 4 line pipeline started as a single command that was gradually refined into something that actually solves a complicated problem. This talk demonstrates the part that isn&#x27;t included in the the usual tutorials or &quot;cool 1-line command&quot; lists: the cycle of &quot;Try something. Hit up to get the command back. Make one iterative change and try again.&quot;<p>[1] You might know him from his other hilarious talks like &quot;The Birth &amp; Death of JavaScript&quot; or &quot;Wat&quot;.<p>[2] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=sCZJblyT_XM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=sCZJblyT_XM</a>