,
6 tweets,
2 min read
Read on Twitter
While working on #TidyFirst this visualization of why software design is a human relationship problem popped up. Thread 
The cliche product/engineering split has someone with an idea waiting for the behavior of the system to change so they can analyze feedback. These are the “waiters” (seems enough time has passed to reuse this word).
The makers actually change the behavior of the system. They also change the structure of the system, because the structure affects how they can change the behavior.
The waiters don’t see and can’t appreciate the structure and it’s changes except indirectly, through the latency, throughout, and variance of the behavior changes.
Software design is the art of building and maintaining the relationship between the waiters and the makers by simultaneously delivering behavior changes and the structure changes necessary to continue delivering behavior changes.
My experience is much fuzzier than this, with ideas coming from makers and structure becoming part of waiter vocabulary and feedback being analyzed all over the place. But software design is still primarily a human relationship problem.
