The notion of a t-shaped developer or t-shaped engineer is becoming more popular in IT companies of all sizes, and the likelihood is that you have come across this term before. But what exactly is a t-shaped engineer? Are you already one? And if not, how can you become a t-shaped engineer? Let’s find out.
First though, a quick note on the use of ‘developer’ vs ‘engineer’: While many in the industry will argue for clear distinctions, the two terms are often employed interchangeably and their use is often influenced simply by which side of the Atlantic you live on or personal preference. Author Gabriel Negreanu prefers ‘engineer’, so that is the term you will find throughout this piece.
Traditionally, companies favoured I-shaped engineers. These were individuals specialised in a single field with little to no knowledge of other stages in the software development life-cycle (SDLC). They had an in-depth understanding of their core area and were very good at their specific job. In fact, everyone in an organisation had very clearly defined roles and generally only interacted with other specialisms at specific stages of a project.
But this structure, neat and tidy though it was, had a disadvantage. The grey areas outside one’s core remit would often be contested by several individuals or teams; or sometimes be void of any one person claiming responsibility. And having many individuals with core competencies but no understanding of each other’s work also resulted in miscommunication and misunderstandings. Overall, this set-up created a lot of workflow inefficiencies which resulted in project mismanagement and lost revenue.
In response to perceived shortcomings of the old model, companies began to revise the scope of engineer positions. By broadening the skill set of the traditional engineer, the ‘I’ came to resemble a ‘T’. T-shaped engineers, then, are still highly skilled in their core field but also have a good working knowledge of other related subjects. As a T-shaped engineer you have a particular specialisation but can also work with others in your team across the SDLC because you speak their language - and they yours. Continuous education and growth are key to this concept.
It is true that t-shaped engineers are not always as strong in their field as their I-shaped counterparts because they do not have the same level of focus on the core aspects of their work. But the benefit to the team and the project generally outweighs this slight lack of specialisation because collaboration and product quality are much improved by this.
There are many benefits to becoming a multi-skilled engineer:
There is no silver bullet or quick fix to becoming a multi-skilled developer, but a few practices will set you on the right path: