[karmakaze]

I wasn't recommending that they all be fired. Ideally some number of them would be redistributed across other teams. What is often inefficient is keeping a large team around that has largely fulfilled their goals.

Also performance is too large an area to make it a single team. It is better to have a database expert guild (or team) that other teams can consult for performance and other engineering quality issues and similarly for other performance sensitive areas. I can't speak for security but I imagine that each area should have experts that cover security for that area.

Perhaps others like working cleaning up poorly written non-performant designs and code but I prefer starting earlier in the process and building it into the engineering culture.

Edit: I think it's actually easier to have a performance/security team at a medium scale of growth. At small scale they would be in the product dev teams or known by name by all teams. At large scale I don't think they can't cover the surface area/volume produced by all the teams. So it should be more effective to develop mechanisms/processes and culture.