From 2b9ec88f04e11a6f7f1247f914afa839e8d5a140 Mon Sep 17 00:00:00 2001 From: "Matt Goldman [SSW]" Date: Tue, 5 Nov 2024 16:08:22 +1100 Subject: [PATCH] Update rules/avoid-using-your-name-in-client-code/rule.md Co-authored-by: Daniel Mackay [SSW] <2636640+danielmackay@users.noreply.github.com> --- rules/avoid-using-your-name-in-client-code/rule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/avoid-using-your-name-in-client-code/rule.md b/rules/avoid-using-your-name-in-client-code/rule.md index 947f904dd8..191b33d778 100644 --- a/rules/avoid-using-your-name-in-client-code/rule.md +++ b/rules/avoid-using-your-name-in-client-code/rule.md @@ -21,7 +21,7 @@ related: guid: 7d9eb8d3-4522-40c9-bcbd-b22f48f50edf --- -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. +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.