Understanding Developer Typology
Ahead of the June Leaders in Tech: Baden-Württemberg held on 21st June 2018 we speak with 1&1’s Matthias Wittum, Head of the Source Center and Christian Rehn, Software Developer in 1&1’s Customer Selfcare Solutions about their highly developed frameworks and models which are specially designed to examine developer typology. Their frameworks and models are proven to support developer teams, strengthen communication and optimise design decisions.
Matthias Wittum explains that whilst working with Christian Rehn, they identified how different developers can be when it comes to reaching a design decision and how this has an impact on the development teams. We know that developers are unique problem solvers who draw on different approaches, knowledge, cultures, experience and principles to produce software solutions. Developers naturally approach projects uniquely, and the outcome can play to a particular focus or strength. Of course within a development team this can lead to several solutions being found and so the challenge is often finding one team solution or design route.
There are enough personality tests out there, but no tests or frameworks based specifically on developers. We felt that some instruments were needed to enable better production efficiency and to help develop teams according to their orientation and typology, so we started filling the gap. That’s how the Design Types Model for instance, came to fruition. It sets out to define developers’ typology via a relatively straightforward base of questions for each developer to answer. The answers provides help classify their typology and then you can group them accordingly. Using this model makes it easier to gain an impression of whether the tasks, the way of working and the environment are a good fit.
Here are three Models which we have formulated to identify developer typology, aid better case arguments to reach design decisions more quickly and to help optimise development teams:
- Design Types Model – sets out to identify why software design is individual and often leads to discussions with colleagues.
- Design Cards – great interactive tool using a set of predefined cards used to aid technical discussions by using proven arguments.
- Design Matrix – helps you to examine technical problems from all perspectives.
Read more about these interactive Models here.
Ever since the agile movement, technical decisions are increasingly discussed or reviewed within the team. Collective Code Ownership means that everyone is now jointly responsible for the software and as a result, it is important for developers to be able to argue precisely and comprehensively, to be able to put oneself into the motives of your colleagues. With our models, we want to support exactly this and strengthen communication in development teams.
Leaders in Tech
Thanks to those who joined us at our Leaders in Tech: Baden-Württemberg meetup held on 21st June 2018 when Matthias and Christian give a complete overview of the developer typology, as well as the Design Cards and the Design Matrix. As a start, to understand the concepts and the overall context.