Are you actually a "generalizing specialist" (or "T-shaped") developer, as is essential in a cross-functional-team? The point of that is to eliminate bottlenecks by being able to help others on the team, & also reduce the bus factor. It's about eliminating silos. 1/3
If somebody gets sick, somebody else has to fill in. Since the team needs all the skills to take an idea to deployment, that means that UI/UX skills, product skills, architecture skills, testing skills, &c. must be evident in more than one team member. 2/3
Programmers who know nothing but coding (e.g. they know a handful of frameworks and languages, but nothing else) are not T-shaped developers. If that's you, it may be time to get out the books or take a class. 3/3
