3 ms·
The article implies that you should architect your system around your existing team boundaries. This is harmful and counterproductive. You should identify the s
by tzahola 9y ago
The article implies that you should architect your system around your existing team boundaries. This is harmful and counterproductive. You should identify the sub-units of your system first, and then you can come up with an organizational structure that work effectively with your architecture.
- reificator 9y agoThat might work for software companies. Doesn't hold up in my experience in companies that happen to need software.
- taspeotis 9y agohttps://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law
- icebraining 9y agoI think the idea is that you've already done that on the backend, and you're just extending it to the frontend.
- tyingq 9y agoThere are unique downsides of extending it there. Bloated downloads and less caching benefit since pages need competing frameworks. How to deal with shared elements like a cart widget or login widget. Overlap...search results and shopping pages may be very similar on an ecommerce site. Their example shows those as 2 separate teams able to make all of their own stack decisions.
- coldtea 9y agoBecause there's some misguided assumption that what fits one domain should fit the other too.