Strategy — Explicit Over Magic

When to use

• The task asks for clear, readable, maintainable code, or the code will be read and extended by a team over time.
• The task is to untangle or clarify code that currently relies on magic methods, global state, or clever indirection.
• The design is tempted to use dynamic properties, __call, __get, or global state to avoid writing out explicit members.

When NOT to use