System Design Heuristics
System Design Heuristics
About the Book
You'd think that after publishing books for half a century, I'd know how to write a book. If that's what you think, you'd be wrong.
Sure, I've even written a book on writing books (Weinberg on Writing, the Fieldstone Method), and I've applied those methods to dozens of successful books. But way back around 1960, I started collecting notes on the process of design, thinking I would shortly gather them into a book. Back then, I didn't call these bits and pieces "fieldstones," but that's what they turned out to be: the pieces that, when assembled properly, would ultimately become my design book.
Ultimately? Assembled properly? Aye, there's the rub!
Building walls from randomly found fieldstones requires patience. So does writing books by the Fieldstone Method. My Introduction to General Systems Thinking took fourteen years to write. But a writer only lives one lifetime, so there's a limit to patience. I'm growing old, and I'm beginning to think that fifty years is as close to "ultimately" as I'm going to get.
So, I've begun to tackle the task of properly assembling my collection of design fieldstones. Unfortunately, it's a much larger collection that I'd ever tackled before. My Mac tells me I have more than 36,000,000 digitized bytes of notes. My filing cabinets told me I had more than twenty-five pounds of paper notes, but I've managed to digitize some of them and discard others, so there's only a bit more than ten pounds left to consider.
For the past couple of years, I've periodically perused these fieldstones and tried to assemble them "properly." I just can't seem to do it. I'm stuck.
Some writers would say I am suffering from "writer's block," but I believe "writer's block" is a myth. I've published three other books in these frustrating years, so I can't be "blocked" as a writer, but just over this specific design book. You can hear me talk more about the Writer's Block myth on YouTube
but the short version is that "blocking" is simply a lack of ideas about how to write. I finally decided to take my own advice and conjure up some new ideas about how to write this design book.
Why I Was Stuck
To properly assemble a fieldstone pile, I always need an "organizing principle." For instance, my recent book, Do You Want to Be a (Better) Manager? is organized around the principle of better management. Or, for my book, Errors, the principle is actually the title. So, I had been thinking the organizing principle for a book on design ought to be Design.
Well, that seemed simple enough, but there was a problem. Everybody seemed to know what design is, but nobody seemed able to give a clear, consistent definition that covered all my notes. I finally came to the conclusion that's because "design" is not one thing, but many, many different things.
In the past, I ran a forum (SHAPE: Software as a Human Activity Practiced Effectively) whose members were among the most skilled software professionals in the world. We held a number of threads on the subject, "What is Design?" The result was several hundred pages of brilliant thoughts about design, all of which were correct in some context. But many of them were contradictory.
Some said design was a bottom-up process, but others asserted it was top-down. Still others talked about some kind of sideways process, and there were several of these. Some argued for an intuitive process, but others laid out an algorithmic, step-by-step process. There were many other variations: designs as imagined (intentional designs), designs as implemented, and designs as evolved in the world. All in all, there were simply too many organizing principles—certainly too many to compress into a title, let alone organize an entire book.
After two years of fumbling, I finally came up with an idea that couldn't have been implemented fifty years ago: the book will be composed of a variety of those consulting ideas that have been most helpful to my clients' designers. I will make no attempt (or very little) to organize them, but release them incrementally in an ever-growing ebook titled Design Heuristics.
How to Buy System Design Heuristics
My plan for offering the book is actually an old one, using a new technology. More than a century ago Charles Dickens released many of his immortal novels one chapter at a time in the weekly newspaper. Today, using the internet, I will release System Design Heuristics a single element at a time to subscribing readers.
To subscribe to the book, including all future additions, a reader will make a one time payment. The price will be quite low when the collection is small, but will grow as the collection grows. That way, early subscribers will receive a bargain in compensation for the risk of an unknown future. Hopefully, however, even the small first collection will be worth the price. (If not, there will be a full money-back guarantee.)
Good designs tend to have unexpected benefits. When I first thought of this design, I didn't realize that it would allow readers to contribute ideas that I might incorporate in each new release. Now I aware of that potential benefit, and look forward to it.
Before I upload the first increment of System Design Heuristics, I'll wait a short while for feedback on this idea from my readers. If you'd like to tell me something about the plan, email me or write a comment on this blog.
Thanks for listening.
- Why I Was Stuck
- How to Buy System Design Heuristics
- About the Author
- What Is Design?
- Misconception: Only Designers Design
- Misconception: Design Is Higher Status
- Marking the Boundaries
- The Great Wall of China syndrome
- Meeting the Natives
- Building Cultural Bridges
- What Versus How
- Who Matters?
- When Does Design Happen?
- Why Do We Need Design?
- How Much?
Learning the Magic of Design
Luck and Magic in Design
- Three wishes
- Return to zero
- Luck and Magic in Design
How Design Begins
- What Must Not Change?
- A Solution Looking for a Problem
- Designing This Book
- Why Are We Doing This?
- A Zero-Level Example
- Random designs
The Rule of Three
- A bet I lost
- The Rule of Three
- The Rule of Three in problem definition
- The Rule of Three in software testing
- The Rule of Three in designing
Loosening Up Your Thinking
- Look for Analogies
- Move to Extremes
- Look Outside the Boundary
- Look for Alibis Versus Explanations
- The Emotional Component
- The Incongruence Insight
- Brown’s Brilliant Bequest
Designing with All Sides of the Brain
- A Sequence of Models of Programming
- The Cognitive Side
- Process versus Product
- The Emotional Side
- An Improved Model of Programming
- The Neglected Models
- Moral Models
- The Social Environment
Where Ideas Come From
- Theft Plus Error
- Design Wagers Checklist
KISS, or Keyp Itt Simpel Stoopid
- Why Must Designers Simplify?
- The Square Law of Computation
- People are different
- Satisfying expectations
The Cybercrud Cudgel
- A Word to designers
- Double design examples
- What’s necessary to succeed in double-design
- Putting Two Problems Together
- Jim’s Estimation Exercise
- Bonus Meta-questions:
- Some answers
- How Design Begins
Heuristics About Getting Information
- Heuristics About Asking Questions
- Some difficult questions
- The Guinness Book of Records exercise
- The perfect method of ranking
- Not all visualizing is visual
- Changing point of view
Bad Decision Making
- Control by eyebrow
- A lousy decision process
Designing to Intimidate
- The History and Psychology of Intimidation
- The IT Center as Intimidator
- They’ll Be Back
- Filling in forms
- Insolent error messages
- Big bad manuals
- Rude treatment
- Slow service
- What’s Our Business, Anyway?
- Who does your design intimidate?
Who uses the system?
- The anthropology exam
- The first ATM robbery
- The plumber on the stock exchange
- Changing point of view
- Tradeoffs change with time
- Features become errors
- The First Law of Software Engineering
Performance By Design
- The First Searching Axiom
- The Second Searching Axiom
- Divide and conquer
- Binary search
- The First Foundation of Effective Computing
- The Second Foundation of Effective Computing
- The Third Foundation of Effective Computing
In Praise of Efficiency
- Is enough enough?
- Worst-first optimization
- The First Rule of Optimization
- The Curse of Optimization
Now versus later
- What do we know about the future?
- Robust Designs
- What do we know about the past?
- Standard parts
- Dispersion of work
- Dispersion of demands
- Large numbers of users
- Hack Attract
- Growth produces bigness
- The Astronomical Test
- How much output?
- Failing to scale
- Long-life systems
- The JIGSAW analogy
Passing to the limit
- Light loads
- Designing the startup
- The Tragedy of the Commons
- The Public Address Law
- Problem avoidance through modularization
- Fully integrated?
- Poor modularization
- Interface treaties
- Management support for design
- The Axiom of Experience
- Fisher’s Fundamental Theorem of Natural Selection
Designs change their assumptions
- A FORTRAN story
- Implementation challenges assumptions
- The Highway Law
- A Design So Bad It’s Good (for a Laugh)
- Every designer’s ideas must be tested
- Example: Out-of-date documents
- How Important Are Design Reviews?
- General rules about reviews
- Which design level is the better choice for reviews?
- What about reviewing logical vs. physical design?
- Isn’t correct or incorrect a matter of opinion with designs?
- Is it possible, then, to develop checklists for design reviews?
- The BCS Preliminary Design Document Review Checklist
Heuristics for designer behavior
- Congruence with tools
- Be as direct as possible
- Know why
- Say why
- Be wary of your tools
- Stay congruent with what’s important
- Who defines goodness?
- Political vs. technical solutions
- Know about people
- Care about people
- Designs or excuses?
- Blaming the victim
- A drastic design approach
- A reasonable design approach
- Use people as a valuable resource
- Ford’s Fundamental Feedback Formula
- Average or extreme?
- What constitutes design success?
- Leading the people
- Delegating tasks
Also By Gerald M. Weinberg
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
C++ Best PracticesJason Turner
Level up your C++, get the tools working for you, eliminate common problems, and move on to more exciting things!
Functional Design and ArchitectureAlexander Granin
Software Design in Functional Programming, Design Patterns and Practices, Methodologies and Application Architectures. How to build real software in Haskell with less efforts and low risks. The first complete source of knowledge.
OpenIntro StatisticsDavid Diez, Christopher Barr, Mine Cetinkaya-Rundel, and OpenIntro
A complete foundation for Statistics, also serving as a foundation for Data Science.
Leanpub revenue supports OpenIntro (US-based nonprofit) so we can provide free desk copies to teachers interested in using OpenIntro Statistics in the classroom and expand the project to support free textbooks in other subjects.
More resources: openintro.org.
R Programming for Data ScienceRoger D. Peng
This book brings the fundamentals of R programming to you, using the same material developed as part of the industry-leading Johns Hopkins Data Science Specialization. The skills taught in this book will lay the foundation for you to begin your journey learning data science. Printed copies of this book are available through Lulu.
C++20 is the next big C++ standard after C++11. As C++11 did it, C++20 changes the way we program modern C++. This change is, in particular, due to the big four of C++20: ranges, coroutines, concepts, and modules.
I am a Software Engineer and I am in ChargeAlexis Monville and Michael Doyle
I am a Software Engineer and I am in Charge is a real-world, practical book that helps you increase your impact and satisfaction at work no matter who you work with.
In the book, we will follow Sandrine, a fictional character who learns to think in a new way enabling her to take a different course of action.
Invest In Digital Health - The Medical Futurist's GuideDr. Bertalan Mesko
Artificial Intelligence and Digital Health are booming. In this book, we explain why now it's a good time to invest in Digital Health and give recommendations on where to invest by looking at the top 24 technological trends we find the most promising.
Atomic KotlinBruce Eckel and Svetlana Isakova
For both beginning and experienced programmers! From the author of the multi-award-winning Thinking in C++ and Thinking in Java together with a member of the Kotlin language team comes a book that breaks the concepts into small, easy-to-digest "atoms," along with exercises supported by hints and solutions directly inside IntelliJ IDEA!
The Hundred-Page Machine Learning BookAndriy Burkov
Everything you really need to know in Machine Learning in a hundred pages.
Mastering STM32Carmine Noviello
With more than 600 microcontrollers, STM32 is probably the most complete ARM Cortex-M platform on the market. This book aims to be the first guide around that introduces the reader to this exciting MCU portfolio from ST Microelectronics and its official CubeHAL.
Software Architecture for Developers: Volumes 1 & 2 - Technical leadership and communication
2 Books"Software Architecture for Developers" is a practical and pragmatic guide to modern, lightweight software architecture, specifically aimed at developers. You'll learn:The essence of software architecture.Why the software architecture role should include coding, coaching and collaboration.The things that you really need to think about before...
The Future of Digital Health
6 BooksWe put together the most popular books from The Medical Futurist to provide a clear picture about the major trends shaping the future of medicine and healthcare. Digital health technologies, artificial intelligence, the future of 20 medical specialties, big pharma, data privacy and how technology giants such as Amazon or Google want to conquer...
Cisco CCNA 200-301 Complet
4 BooksCe lot comprend les quatre volumes du guide préparation à l'examen de certification Cisco CCNA 200-301.
CCDE Practical Studies (All labs)
3 BooksCCDE lab
"The C++ Standard Library" and "Concurrency with Modern C++"
2 BooksGet my books "The C++ Standard Library" and "Concurrency with Modern C++" in a bundle. The first book gives you the details you should know about the C++ standard library; the second one dives deeper into concurrency with modern C++. In sum, you get more than 600 pages full of modern C++ and about 250 source files presenting the standard library...
Modern Management Made Easy
3 BooksRead all three Modern Management Made Easy books. Learn to manage yourself, lead and serve others, and lead the organization.
Programming with Ease
3 BooksAlle drei Bände der Serie Programming with Ease in einem Paket. Darin findest du alles, was ich dir zu den wichtigsten Phasen der Softwareentwicklung im Hinblick auf Clean Code Development für langfristig hohe Produktivität sagen kann.Im Band Slicing findest du die Anforderungsanalyse im Rahmen eines iterativ-inkrementellen Vorgehensmodells aus...
2 BooksUnveil the power of Ansible and Vagrant with this bundle at a special price. You'll have everything you need to get started with Vagrant - learn the basics and how to create your virtual development environments, using Ansible as provisioner! About Vagrant Cookbook Vagrant Cookbook is a complete guide to get started with Vagrant and create your...
2 BooksDocker and Kubernetes are taking the world by storm! These books will get you up-to-speed fast! Docker Deep Dive is over 400 pages long, and covers all objectives on the Docker Certified Associate exam.The Kubernetes Book includes everything you need to get up and running with Kubernetes!
Growing Agile: The Complete Coach's Guide
7 BooksGrowing Agile: Coach's Guide Series This bundle provides a collection of training and workshop plans for a variety of agile topics. The series is aimed at agile coaches, trainers and ScrumMasters who often find themselves needing to help teams understand agile concepts. Each book in the series provides the plans, slides, handouts and activity...