That's a great article Nicola, very well written and articulated. You set a high bar :)
Regarding the T-shaped - when I think about it, what mostly comes to mind is the technological expertise. The example you gave is in very different skills: Code/Hardware/Leadership/Design/Cloud. Being a specialist in code is kind of general.
That's a great article Nicola, very well written and articulated. You set a high bar :)
Regarding the T-shaped - when I think about it, what mostly comes to mind is the technological expertise. The example you gave is in very different skills: Code/Hardware/Leadership/Design/Cloud. Being a specialist in code is kind of general.
I imaging a specialist being a Python developer, a T-shaped being a backend developer with Python preferences, and a generlist a fullstack developer :)
Thanks, Anton! I think it all depends on the zoom level. I'm a natural-born Generalist, and what you see there comprises a good part of my area of expertise, which I then narrowed down to Specialists and T-Shaped. If you look at it from a developer's point of view, what you wrote would definitely apply better 🙂
Yeah, I understood your POV, and I'm a bit similar in that case. But in the context of building teams, people usually think about those terms in a more technical sense.
That's a great article Nicola, very well written and articulated. You set a high bar :)
Regarding the T-shaped - when I think about it, what mostly comes to mind is the technological expertise. The example you gave is in very different skills: Code/Hardware/Leadership/Design/Cloud. Being a specialist in code is kind of general.
I imaging a specialist being a Python developer, a T-shaped being a backend developer with Python preferences, and a generlist a fullstack developer :)
Thanks, Anton! I think it all depends on the zoom level. I'm a natural-born Generalist, and what you see there comprises a good part of my area of expertise, which I then narrowed down to Specialists and T-Shaped. If you look at it from a developer's point of view, what you wrote would definitely apply better 🙂
Yeah, I understood your POV, and I'm a bit similar in that case. But in the context of building teams, people usually think about those terms in a more technical sense.