liveBook · Manning

Pull-based design

As explained in Build High Value Software Systems

A design pattern in which concrete requirements pull only the structure needed to satisfy them into a codebase.

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

How Build High Value Software Systems covers it

How deep it goes
Defines pull against speculative push and illustrates increasing abstraction through three notification implementations.
Examples
Shows email first, conditional SMS next, and a four-channel notification pattern as requirements grow.
What you can do after
Evaluate whether a concrete requirement justifies adding an abstraction to the codebase.
How it connects
Connects YAGNI with Lean thinking and contrasts pull-based design with speculative design.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.