Discussion about this post

User's avatar
Vasco Duarte's avatar

I love the balanced discussion of the different options, and how you started with the story of how the problem develops over time.

We often read solutions that are focused on showing "the perfect solution" (tm), but in the end ignore the fact that code, architecture, team structure, all evolve over time, and what is a great solution today, won't be tomorrow!

But I miss something fundamental. It's not core to your article, but by not talking about how the organization affects architecture choices I think you are missing a key piece that is key for managers wanting to keep their architecture appropriate over time (not just find "the perfect solution" (tm)).

You don't discuss Conway's Law and how the choices we make in organization affect the architecture that the code ends up manifesting.

In other words, your article is missing the people+organization aspect of the very same problem. And I think it will inform your proposed solution, but also validate some other solutions depending on the context of the reader.

Expand full comment
2 more comments...

No posts