3 ms·
Well, I think this so nicely points out the differences between a solution that comes from the top versus one that comes from the bottom. It could almost even
by supernova87a 6y ago
Well, I think this so nicely points out the differences between a solution that comes from the top versus one that comes from the bottom.
It could almost even illustrate the pitfalls and hopes of someone architecting without the details, and saying "just make it work!"
When you plan from the top, you leave the details (and pain) to someone else to work out. There are 10,000 little problems that you don't have time to think through and delegate it down to the people day-by-day to figure out how to fit into your symbol of clean order. (and often don't or can't, leading to anger at the top when details don't cooperate)
Versus when people work out their patchwork of little agreements with each other to their temporary satisfaction to get on with life every day, it works but has no coherent direction to it. Like a coral reef figuring out how to grow -- somehow every little piece figured out how to live, but no one exactly told it how to do so.
It is to be marveled at in the rare cases when someone from the top designs something with the reality of the bottoms-up in mind, and can make it work.