Design

Code, component, and API design evaluation.

Abstraction Quality

Naming

• Does processData() actually process data?
• Do names reveal intent?
• Consistent vocabulary (don't mix "user" and "account" for same concept)?

Red flags:

• Manager, Handler, Processor, Utils — often god classes
• Single-letter names outside tight loops
• Abbreviations that aren't universally known

Single Responsibility