[ericand]

Summarized well by these lines:

> Back in the day, front end, back end, operations, and DBAs separated because they needed different skills. Now we accept that a software team needs all the skills. We group by responsibility instead — responsibility for business value, not for activities

> We once layered by serving data to software. Now we layer by serving value to people.

This is a nice narrative for the rise of developer products, where there used to not be a market.

[vvanders]

Andy Grove's High Output Management(hate the name, like the book) also talks about this tension between teams that focus on the business unit and the horizontal teams that support(if I recall correctly he groups in marketing, finance, and others) the business units.

You get large advantages in having teams built around specialized functions, however at the cost of lower cohesion.

Business verticals will trade all sorts of advantages for that cohesion.

There's tension in finding the right mix, the book covers it much better than I can but it's interesting to see parallels in tech stacks as well.

[insulanus]

> however at the cost of lower cohesion

Is that cohesion within the team, or across teams (in the company as a whole)?