[nathanielks]

> Instead there’ll be a much stronger focus on teams of generalists, or combined teams of specialists from different fields, working on a feature or product end to end.

> Coordination has in my experience always been the big bottleneck in getting anything done

I work at a large enterprise you've heard of. They're currently re-organizing the product area to remove currently-static two pizza teams into an amorphous blob of feature-oriented teams. Once the feature is complete, the team is dissolved and the engineers re-enter the pool, tasked with new features.

All that to say, I think you're right on the money with your assessment.

[NewLogic]

Where does the feature go for long term ownership? That throws you build it you own it out the window. We are going to get more time for documentation and handover right, right? Engineers are famous for generating good documentation.

[materielle]

There’s going to be lots of documentation. It will be AI generated and no human will ever read it. But there will be a lot of it.

[jon-wood]

Some places I've worked in the past had a rotating support team who were tasked with dealing with bugs/small feature requests/incidents for a period. I'm not sure that's the right answer because nobody wants to be on the team that's just doing scutwork even if its just for a month or two but it is an option.

[nathanielks]

All fantastic questions I wish we had an answer for