title: Typical pitfalls to avoid for BASH beginners.
body: <p>The other day I answered a question where it was necessary to loop through all the sub-dictionaries in a given directory. </p>
  
  <p>As a self-taught bash user I quickly answered the question. However, in my answer I used <code>for DIR in $(find ...); do "something"; done</code> to loop through the sub-directories. A polite bash guru pointed out that if I continue with bad habits like that will one day find myself in a lot of trouble.</p>
  
  <p>While correcting my answer I found that I had (embarrassingly) many more bad habits. I could not find any topic like this on stackoverflow, but I am sure there are many people like me at a "beginner(++)" level with bad habits based on methods that "sort-of-works".</p>
  
  <p><strong>My question is generic albeit simple:</strong></p>
  
  <p>What are important/damaging pitfalls to avoid for someone who is using bash? <em>(If you find the question to generic to answer I would appreciate a short description of the case with link to documentation or another SO question regarding the subject is appreciated.)</em></p>
  
  <p>E.g. When performing loops to edit files/dirs, using globb characters, pipes, logicals, short hand notation (i.e. <code>``</code>) and <strong>last but not least</strong> applying functions for purposes which they should not be used.</p>