Complexity makes code harder to understand, follow, and change. During review, it can appear as giant classes, too many layers for a simple method, excessive abstraction, or temporary workarounds whose original intent is unclear. section 4.4.4 section 3.3.1
Use these questions to decide whether complexity deserves attention:
- Can another developer understand the code now and when revisiting it later? section 3.3.1
- Is the structure human-friendly and straightforward, or must readers jump through layers and abstractions to follow a simple method? section 4.4.4 section 3.3.1
- Do workaround or temporary parts need a more permanent solution? section 3.3.1
- If the same complexity problem escapes linting or prechecks repeatedly, consider a new linting rule or a precheck adjustment after the third recurrence. section 4.4.4
