"A team of developers comprises several roles..."

I disagree. This might be true at smaller companies where having "one of everything" on a team leads to a mix of dissimilar skills, but in "moderately large" and larger companies my experience is you need teams of people with THE SAME skills working on their piece of the enterprise codebase. Having the same narrow focus and ability when it comes to specialization helps significantly in these cases because if you hit a road block then talking with your team mate about the issue it's a glorified rubber duck exercise but a true back and forth from which knowledge can be gained.

I also take issue with how a Team Lead is defined. In my experience the titles Team Lead and Software Dev Manager vary so much from company to company that the titles mean far less than a description of what the people holding those titles actually do. I've seen SDMs who code 50% of the time and I've seen Team Leads who did nothing but attend meeting and spend the whole day deconflicting expectations between product and engineering teams so that upcoming specs actually make sense and aren't a pile of contradictions and nonsense by the time they land on the lap of the developers who need to convert the vision into running code.

This is a pretty good example of content marketing done poorly. Superfluous content, somewhere between 98% and 99% opinion, the rest just incorrect. And it seems to taken about ten minutes to write and throw up onto the blog. If they made the memes that would have taken longer than writing the piece.

With the exception of the team lead, all of these stereotypes have quite serious dysfunctions which likely clash with each other and could easily derail a project.

In a team like this, the tech lead would likely end up spending most of their time managing the conflicting goals and personalities leading so impaired productivity.