this post was submitted on 19 Aug 2023
33 points (94.6% liked)
Experienced Devs
3979 readers
1 users here now
A community for discussion amongst professional software developers.
Posts should be relevant to those well into their careers.
For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:
- Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes, I have built both types - specialist first and it was a fiasco. Cross-functional was consistently the best
I'm a little surprised specialist was bad. Unless bad egos were involved.
Specialist is too thin. The specialists only know what they know and they don't want to learn new things outside their speciality. So I had to hire a new person everytime we found a speciality gap because the specialists were like "not my job, I am an X specialist, go hire a Y specialist". Then, they held their work tightly, no cross training, so the specialists all became their own brand of bottleneck. Different work speeds and different levels of quality meant that ego came to defend against performance complaints, and I as a manager couldn't add more people to the problem areas because they weren't trained in that area and the specialist could do it faster than they could train others to help.
That being said, all my full-stack team members had specialities. That's what T-shaped means. I had frontend specialists who could work the whole stack, backend specialists who could work the whole stack. Dev tools specialists who could work the whole stack. Architects who could work the whole stack. Everyone we hired had something they were best at, and an alignment to learn the whole stack. Within a year they were able to work on all tech in the stack and anyone could bring in a new tech to solve a problem and everyone would learn it.