Write helpful error messages -- the users first debugging tool

Vague error messages force users to guess what happened. Developers waste time debugging self-explanatory issues.

Every error message should answer: What happened? Why? How to fix? Format: Failed to [action] because [reason]. [Fix suggestion]. Include relevant values but never secrets.

Error messages are the most-read documentation. A good one eliminates a debugging session.