Do you use meaningful modifiers for custom implementations?

Updated by Tiago Araújo [SSW] 9 months ago. See history

123
<introEmbed body={<> When creating custom controls, avoid vague or generic names like CustomStepper or CustomDbContext. Generic terms like “custom” or “base” don’t communicate what makes the component unique, and they add little value for other developers. Instead, use meaningful modifiers that describe the component’s specific purpose or customization. </>} />

Why it matters

Meaningful modifiers make it clear what a class, module, or component does or how it differs from a standard version. This helps developers understand its role without digging through code and reduces the chance of naming conflicts with other libraries.

Naming a custom DbContext implementation CustomDbContext or a specialized input control CustomInput doesn’t provide any real information. It’s unclear what is customized, making it harder to understand and maintain.

❌ Figure: Bad example - A modifier that doesn't tell you what has been modified is of no value

A more descriptive name, like WriteOnlyDbContext or BorderlessTextInput, indicates exactly what’s different about the component, making it easier to understand its function at a glance.

✅ Figure: Good example - A modifier that clearly conveys what is different from the original can save developers time reading through the code

Categories

Rules to Better Naming Conventions

Acknowledgements

Matt Goldman
Jeoffrey Fischer
Daniel Mackay
Related rules

Need help?

SSW Consulting has over 30 years of experience developing awesome software solutions.