As an architect for a team with a large number of people, I have a couple of problems:
- I often make decisions that turns out to be quite crappy.
- Even when I think I’ve written or drawn something that’s smart, it often turns out that it’s incomprehensible to everyone else
Luckily, I’ve noticed that most developers have characteristics that almost always counter these weaknesses:
- Most developers are pretty smart, especially when they’re trying to solve a specific problem.
- Most developers don’t read architecture documentation
So instead of trying to force the developers to read my crappy, poorly documented decisions, I decided to try to see what happened if I instead made use of the opportunities that the situation presented to me. Enter: The Great Wall of Architecture.
There are two rules for the Great Wall of Architecture:
- Only the pictures on the Great Wall of Architecture are officially part of the system documentation.
- The architect (me) cannot draw pictures to be included on the Great Wall of Architecture
As a playful addition, some of the developers have signed their work, just like we used to do in kindergarten. You can’t actually see it on the photo, but the hand writing on this diagram reads “made by Christin, 32 years old”.
My hope is that the Great Wall of Architecture will make the whole team feel they can use their strengths on the project. As more drawings come up every day, I’m optimistic with the result.