clean-code

Start with the Boy Scout Rule: leave each file cleaner than you found it. Extract small functions that do one thing, replace flag arguments with separate functions, remove duplication, and rename variables to reveal intent before changing behavior.

Functions should be small (two to four lines is normal), do one thing at one level of abstraction, take zero to two arguments, avoid flag arguments and side effects, and follow Command-Query Separation. Descriptive long names beat short cryptic ones.

Yes, the principles are language-agnostic: naming, function size, DRY, error handling, and test discipline apply everywhere. Language-specific notes exist, such as C# interface naming conventions and .NET thread-safe collections, but the heuristics transfer.

Comments are a necessary evil used only to compensate for failure to express intent in code. Good uses include legal notices, intent explanation, warnings of consequences, and public API documentation. Redundant, misleading, or commented-out code should be deleted.

F.I.R.S.T means tests should be Fast, Independent, Repeatable, Self-validating, and Timely. Each test covers one concept using Arrange-Act-Assert structure, and test code must stay as clean as production code so the suite remains maintainable.