Be your own code reviewer and spot bugs early, so that your reviewer can focus on giving you quality feedback and not lose their heads around indentation errors. The Single Responsibility Principle demands “A class should have one, and only one, reason to change” Each function should have a single concise intent.
Table of contents
#1 rule: The reviewer’s time is golden.ClarityFunctionalityTestsAbstractionStyleDocumentationReuse and Duplicated CodeConfiguration and ConstantsDependenciesException HandlingPerformanceInstrumentation4 Comments
Sort: