4 ms·
Parts 1 and 2 are also great reads, as they go into the relationship between the changer and the waiters. It's especially challenging to communicate effectivel
by ereyes01 7y ago
Parts 1 and 2 are also great reads, as they go into the relationship between the changer and the waiters.
It's especially challenging to communicate effectively when the waiter is not a developer. The language of structure vs. behavior is an excellent way to describe the challenges of building a system to a waiter, especially when frustration with a slow perceived pace of behavior change is coupled with a lack of understanding of needed structure. This vocabulary is universal and clearly conveys what is happening- thanks Kent!
- hotcrossbunny 7y agoYou are so right regarding the communication challenge. But rising to that challenge can be immensely rewarding, both on a personal level and for growing a vision for the emerging software. Big ups indeed to Kent for writing about stuff like this, but also to all you folk who thought it was worthy reading and commenting on.
- davidjnelson 7y agoThanks for mentioning this. Read those and indeed fantastic reads. Interleaving structural and behavior changes is brilliant. I already do that, but these write ups give great advice on how to communicate the practice more clearly. Part 2: https://medium.com/@kentbeck_7670/software-design-is-human-relationships-part-2-of-3-waiters-changers-and-sufficiency-4c0bb9a08d23 https://medium.com/@kentbeck_7670/software-design-is-human-r... Part 3: https://medium.com/@kentbeck_7670/software-design-is-human-relationships-part-3-of-3-changers-changers-20eeac7846e0 https://medium.com/@kentbeck_7670/software-design-is-human-r...