Design
Design is the process of planning and specifying an artifact’s structure, behavior, or presentation, and the resulting arrangement, to meet intended purposes and constraints.
Functional Design and Architecture: Examples in Haskell
The creative activity of selecting and organizing software structures and mechanisms to satisfy requirements while managing trade-offs.
- How it is used
- Frames software design as translating requirements and domain models into structures that meet goals while controlling complexity.
- How deep it goes
- Defines design and complexity trade-offs, then illustrates interfaces, patterns, and iterative top-down development.
- Examples
- Uses spaceship control requirements and a thermometer adapter to illustrate design decisions.
- What you can do after
- Evaluate design choices by weighing accidental complexity, maintainability, and requirements.
Read how Functional Design and Architecture: Examples in Haskell explains design →
WordPress Power Toolkit: Harness AI to build next-level websites
Site design is the planning and creation of a website's visual appearance, layout, and user-facing presentation.
- How it is used
- Shapes a WordPress site’s appearance to suit its audience and purpose rather than relying on an unchanged theme.
- How deep it goes
- Explains theme controls and screenshot-based critique, but does not teach color theory or typeface variation systematically.
- Examples
- Uses contrasting recipe home pages, an awkward potato image, Canva templates, and a water-garden site scan.
- What you can do after
- Operate/configure it in WordPress, explore Canva alternatives, and evaluate AI suggestions against a site’s goals.
Read how WordPress Power Toolkit: Harness AI to build next-level websites explains design →
Collaborative Software Design: How to facilitate domain modeling decisions
Software design is the activity of determining a software system’s structure, behavior, and implementation decisions from its requirements.
- How it is used
- Guides collaborative activities that move a current software system from understood problems toward a preferred system.
- How deep it goes
- Defines design, distinguishes architecture, and connects modeling with facilitation, bias, explicit decisions, and iterative feedback.
- Examples
- Uses BigScreen modeling, boundary decisions, ambiguous terminology, architectural disagreements, and evolving decision records as practical examples.
- What you can do after
- Apply it via collaborative modeling to expose assumptions, make decisions, plan system changes, and keep designs adaptable.
Acing the Frontend Interview
System design is the practice of defining the architecture, components, interfaces, and operational characteristics of a software system.
- How it is used
- Frames system design as a core frontend-interview activity for evaluating architecture, scalability, performance, and collaboration.
- How deep it goes
- Extends beyond implementation into trade-offs, backend dependencies, edge cases, testing, and failure handling without specifying detailed internals.
- Examples
- Uses a React star-rating component, interview follow-up questions, and a four-stage frontend interview process.
- What you can do after
- Evaluate/understand frontend architectures and articulate implementation reasoning, trade-offs, performance concerns, and failure paths.
Design for Developers
Web design is the planning and creation of a website’s visual presentation, structure, and interaction.
- How it is used
- Bridges visual design, user experience, and development so developers can make informed interface decisions.
- How deep it goes
- Explains how research, user experience, visual choices, and implementation fit together, while stopping short of expert-level design training.
- Examples
- Uses interface spacing, signup tracking after a redesign, and project requirements to illustrate design decisions and testing.
- What you can do after
- Apply design fundamentals to refine interfaces, communicate decisions, and test changes against user needs.
The Coder Cafe
Software design is the planning of a software system's structure, components, interfaces, and interactions.
- How it is used
- Frames software structure as relationships among elements whose benefits should guide design.
- How deep it goes
- Defines design through elements, relationships, and benefits, then sharpens relationship analysis with coupling examples.
- Examples
- Uses service dependencies, control coupling, and temporal coupling to illustrate relationships requiring precise analysis.
- What you can do after
- Evaluate how relationships between elements shape software design and why vague coupling descriptions are insufficient.
Also covered in
- Practices of the Python Pro
- Software Design for Python Programmers
- Object-Oriented Software Design in C++
- Architecture Modernization: Socio-technical alignment of software, strategy, and structure
- Spec-Driven DevelopmentIn early access (MEAP)
- Machine Learning System Design
- Idiomatic Rust
- "Looks Good to Me"
- Generative AI in Action
- Everyday Data Visualization
- The Art of Unit Testing 3e
- Grokking Simplicity
What to know first
- requirementsA requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
- model architectureModel architecture is the structural arrangement of a computational model’s components, connections, and operations that determines how it processes inputs and produces outputs.
- object-oriented programmingObject-oriented programming is a programming paradigm that organizes software around objects combining state and behavior, often using encapsulation, classes, inheritance, or polymorphism.
- complexityComplexity is the degree to which interacting elements or factors make a system or problem difficult to understand, predict, change, operate, or solve.
Related concepts
- specification authoringpart of · Specification authoring is the process of eliciting and expressing a system’s required behavior, constraints, and acceptance conditions.
- network designincludes · Network design is the selection and arrangement of network components and connections to meet specified operational, performance, capacity, or cost requirements.
- sustainable applicationproduces · A sustainable application is software designed to remain useful, reliable, maintainable, flexible, and deployable throughout a long operational lifespan.
- business problemimplements · A business problem is an organizational need, challenge, or opportunity that a solution is intended to address.
Questions about design
What is design?
Design is the process of planning and specifying an artifact’s structure, behavior, or presentation, and the resulting arrangement, to meet intended purposes and constraints.
Which Manning books explain design?
Functional Design and Architecture: Examples in Haskell, WordPress Power Toolkit: Harness AI to build next-level websites, Collaborative Software Design: How to facilitate domain modeling decisions, Acing the Frontend Interview, Design for Developers and The Coder Cafe.
What should I know before learning design?
Manning books that teach design usually introduce requirements, model architecture, object-oriented programming and complexity first.
What kinds of design are there?
Kinds of design include network design.
What is design part of?
Design is part of specification authoring. Specification authoring is the process of eliciting and expressing a system’s required behavior, constraints, and acceptance conditions.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





