Code that gives good errors beats code that gives none

When you cd into a directory that doesn't exist, the terminal tells you: No such file or directory. It's blunt, but it's actually incredibly helpful: it tells you exactly what went wrong. In the professional world, the quality of error messages defines the quality of software. A program that fails silently is far less trustworthy than one that speaks up and says, "Here's what's wrong."

Errors aren't the enemy. Errors are feedback from the computer. They're the most honest companion you have, telling you what you tried and what didn't work. Once you build the habit of reading error messages, your problem-solving speed changes dramatically.

Don't fear errors. Learn from them. That's the best way to build a relationship with the terminal.