A small C# detail that can make your code cleaner and more efficient: string comparisons. A pattern I still see often is converting strings before comparing them: ❌ Avoid this if (input.ToLower() == "example") { // do something } This approach creates an additional string allocation and also relies on the current culture. A better option in most scenarios is using StringComparison explicitly: ✔ Prefer this if (input.Equals("example", StringComparison.OrdinalIgnoreCase)) { // do something } Why this is usually better: • avoids unnecessary string allocations • makes the comparison intent explicit • prevents unexpected behavior caused by culture-specific rules This becomes even more important in high-throughput services, APIs, or hot code paths where small inefficiencies can accumulate. Clean code is good. But understanding what happens under the hood is what makes a real difference in production systems. Curious how other developers approach this: Do you usually rely on StringComparison, or do you still see .ToLower() / .ToUpper() patterns in production code? #dotnet #csharp #softwareengineering
Cassio Almeron
1mo
Great tip! Simple things that make a difference in the end.
Good point. I still see .ToLower() comparisons in production code, especially in older services. Using StringComparison.OrdinalIgnoreCase makes the intent explicit and avoids unnecessary allocations, which matters a lot in hot paths or high-throughput APIs. Small details like this often have a bigger impact than people expect.