Software Design Philosophy

by wondelaic172996495beMIT2.3K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.

Instructions onlySoftware Development
  1. c172996495beCurrentcommit c172996Published Oct 8, 2026

Source and attribution

Source:wondelai/skillsinsoftware-design-philosophyat commitc172996

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal