C# 12 primary constructors reduce boilerplate when capturing dependencies.

Prefer when:
✅ Constructor only captures dependencies/config
✅ No complex initialization
Avoid when:
✅ Validation or non-trivial initialization is needed
#csharp #codingguidelines #classdesign

Do not use “the AI wrote it” as an excuse during a code review.
AI is a productivity tool, not a substitute for engineering judgment. At least, not yet...

#codingstandards #csharp #codingguidelines #designpractices #bestpractices #ai

When should a C# operation be a method rather than a property?

Use a method if it’s expensive, performs a conversion, returns a different result each call, or causes side effects.

Lazy-loading and internal caching are reasonable exceptions.

#csharp #codingguidelines #codingconventions

Properties should be stateless with respect to other properties. Setting DataSource then DataMember should have the same result as the reverse. Sounds trivial, but I've seen plenty of classes where properties were anything but simple.

#csharp #codingguidelines #classdesign #codingconventions

Prefer a single-method interface when state matters, the contract is strong (IDisposable, IEquatable), default interface methods help, or more members are likely soon. #codingstandards #csharp #codingguidelines #designpractices #bestpractices

...that are used to transfer data over a communication channel, also called Data Transfer Objects, or a class that wraps several parameters of a method. For DTOs, consider using an immutable record type instead of a class to make the intent explicit.

#csharp #codingguidelines #classdesign #

💡 Inversion of Control or Dependency Injection frameworks sometimes require exposing a dependency as a public property. If it's only used for dependency injection and nothing else, I wouldn't consider that a violation.

#bestpractices #codingdesign #codingguidelines #csharp

...class. A less subtle example is not honoring the behavior expected by the base class.

#bestpractices #codingdesign #codingguidelines #csharp

Creating company document for #Sitecore best practices and guidelines, hooray for #codingGuidelines

Apple doesn't always follow them, but they do publish great guidelines of what is okay to abbreviate in code: https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CodingGuidelines/Articles/APIAbbreviations.html

The original "architects" of the codebase may have had a great vision, but that information often gets lost. As a senior developer, I recognize the desire to keep a codebase consistent and tidy. We use #codingguidelines, automated style checkers, and auto-formatting tools. (cont'd)