(noun) The principle that time spent discussing a language feature is inversely proportional to its mathematical complexity.

The committee spent three hours debating syntax highlighting colors but only fifteen minutes on the type system’s soundness proof.

Wadler’s Law describes the tendency for programming language design discussions to focus disproportionately on trivial, accessible features while neglecting fundamental but complex aspects. Named after computer scientist Philip Wadler, the law demonstrates that cognitive accessibility drives participation in technical discourse, often at the expense of addressing the most critical design decisions. This represents a specialized case of Parkinson’s Law of Triviality, commonly referred to as bikeshedding.

Examples:

• Extended debates over bracket styles versus brief reviews of memory management
• Lengthy discussions about variable naming conventions during API design sessions
• Focus on IDE color schemes while ignoring algorithmic complexity analysis
• Committee meetings that prioritize logo design over protocol specification