symmetry

Structural mirroring ensures analogous operations like create_user and create_product follow identical function signatures, parameter orders, and error handling patterns. This reduces cognitive load by making parallel code paths predictable across resources.

Code symmetry is the practice of ensuring parallel code paths like event handlers and matching pairs maintain analogous structure across functions and modules. It improves readability by establishing predictable patterns that make codebases easier to navigate and understand.

You check for structural mirroring violations by reviewing function signatures, return shapes, error handling, naming, file structure, and test structure across matching pairs. This identifies inconsistencies in how analogous event handlers are implemented across modules.

Yes, you can review the consistency of CRUD operations in a specific service by analyzing whether functions performing analogous work like create, read, update, and delete maintain identical signatures and return shapes across different resources within that service.

Common violations include mismatched function signatures, inconsistent return shapes, divergent error handling patterns, unrelated naming conventions, and misaligned file or test structures across analogous operations that should mirror each other.

Strict structural mirroring may not suit parallel code paths with fundamentally different operational requirements or domain constraints. Forcing identical structure on operations that handle distinct business logic or external dependencies can introduce unnecessary coupling and obscure genuine differences.