Author here. The list: EALLCAPS messages, handing non-responsive terminal apps, how to use interpreters, restarting services, running unprivileged apps on low ports - is just based on my own experiences working with people from non-Unix backgrounds.<p>There&#x27;s a few simpler things that also come up:<p>- You don&#x27;t need to close your terminal window to make .bash_profile changes take effect, just run `bash -l` to start a login shell<p>- The find command. Find can do a bunch of stuff, but most of the time you just want:<p><pre><code>    find &#x2F;dir -name &#x27;somefile.ext&#x27;
</code></pre>
If you&#x27;d prefer to type:<p><pre><code>    findname &#x27;somefile.ext&#x27;
</code></pre>
...then here&#x27;s a shortcut for your .bash_profile:<p><pre><code>    function findname () {
        find . -name &quot;$@&quot;
    }

 - journalctl. A lot of folk seem to spend time either hunting for a regex to scrape time or scrolling like a maniac to find a particular time of day. Just:

    journalctl -u myapp --since 09:00
</code></pre>
To get everything that happened since 9AM.