0.6 How not to get stuck

   [ ] Time-box confusion to 20 minutes, then move on -- some things click
       two chapters later, once you've seen the NEXT layer.
   [ ] `man <command>` and `<command> --help` before a search engine --
       building that reflex now pays off for the rest of your career.
   [ ] When a command fails, READ THE ERROR MESSAGE FULLY before acting.
       Linux/kernel error messages are usually precise.
   [ ] Break things on purpose in your lab. You cannot hurt anything by
       experimenting on a disposable VM. Use that freedom.