Naming things

Table of Contents

Why we need guidelines

Engineering wisdom often says that code gets read an order of magnitude more
often it gets written.

Understanding what’s written is paramount to building features, or, more
critically, addressing issues — you wouldn’t want to have to dig into
documentation, or hunt for the appropriate person, when you’re having to
diagnose an incident occuring in production.

Avoid lingo and acronyms

Lingo and acronyms make onboarding engineers much harder. Even after onboarding,
they’re a source of pain as different teams can build up lingo that reflects
their particular concerns.