Pull-based design lets real requirements draw the needed structure into a codebase. Instead of building speculative abstractions for imagined future needs, add complexity when a concrete requirement calls for it. This applies YAGNI to design and is especially useful in legacy systems, where each extra layer adds to what developers must understand and maintain. section 7.3.1
Notification channels
A direct email function handles the first requirement. When high-value orders need SMS, a conditional handles the second. With four channels, shared formatting and a channel-selection pattern earn their place. The structure grows in response to demonstrated needs, not predictions. section 7.3.1
