Do you avoid using your name or your company’s name in client code?

<introEmbed body={<> When building solutions for clients, it’s tempting to include personal or company identifiers in control or component names, like `GoldieEntry` or `SSWButton`. However, naming controls after yourself or your company in client projects can create confusion, dilute the client’s branding, and look unprofessional. For consultants, the goal should be to name components in ways that make sense within the client’s business context. </>} />

Why it matters

Names that reflect the client’s brand or domain are clearer and more meaningful for the client’s internal teams and stakeholders. They also reduce the risk of naming conflicts and make it easier for future developers to understand the purpose of a component in context.

❌ Figure: Bad example - Naming client IP after yourself or your company is not cool

✅ Figure: Good example - Naming client IP with the client's branding is better

Note: This approach is OK to denote a branded version of something, but often it's better to indicate the customization itself in the name. See rule on using meaningful modifiers for custom implementations.