60. Plan for failure
software breaks. hardware fails. services go down. users make mistakes. Anticipate as many failure modes as you can, and design recovery plans and craft reasonable, well written communications for the user. Technical writing is its own topic, but for error messages the important things to accomplish are
a. clearly communicate the situation in language that is relevant to the user demographic. e.g. if it’s not a technical audience don’t use jargon
b. explain what to do next
61. Label your buttons. With words. don’t do clever shit like only showing labels on hover. hidimg the labels is mystery meat navigation.