How to use the Technology Radar
Introduction
Technology Radar is a tool that shows which technologies, tools, frameworks, etc., our company is using, giving a try, holding back, etc., at the moment. Our Technology Radar is subject to change over time and it serves multiple purposes:
- Clients can look at our expertise to get support in their decision to work with us.
- Employees can use radar to get advice on suitable technologies and tools for their project.
- Job Seekers can learn more about the company, how it works, and our vision on modern tooling. This may help to recruit people.
Filtering
You can use these tags below the radar to filter its content:
- coding
- method
- pattern
- qa
- cloudops
- frontend
- backend
- ai
- culture
- iot
- cicd
- database
- security
Quadrants
The topics of the quadrants should remain stable for the years to come. We decided to go with these quadrants:
- Languages & Frameworks: That quadrant includes development languages (such as Kotlin, C# or Golang), as well as more low-level development frameworks (such as Spring Boot or Quasar), which are used in our projects.
- Methods & Patterns: It is probably the most diverse of all quadrants as it contains not only methods and patterns concerning software development, continuous X, testing and software architecutral topics but also topics that define our culture at and organization of
iits-consulting . - Platforms: Technologies related to the operation of software, platforms and infrastructure to run software, tools and services are the topics of that quadrant.
- Tools: That section contains a range of software tools, from small helpers to bigger software projects, that we've come to love.
Rings
The iits technology radar is a collection of technologies and cultural topics that are assigned to rings. The rings are indicators of how strong we agree and promote a topic. For familariy reasons to other technology radars we stick with those for rings:
- ADOPT: Since our technology radar's purpose is to show, what we're using and how we're working, most blibs will be in the center of our radar in the ADPOT ring. The topics in that ring are the field of our collective expertise and recommend to be used.
- TRIAL: Topics that have been assessed and left the impression to be promising may be moved to the TRIAL ring, indicating that we're trying them out in a production environment. Once we've gathered production experience they maybe moved to the ADOPT ring or to HOLD.
- ASSESS: In software and IT business the world is changing very fast. At iits consulting we're constantly watching the changes and experimenting with the new. Some of those topics are mentioned here in that ASSESS ring. Usually, they are not used in production but in sandbox projects or proof of concepts.
- HOLD: The constant change in the IT world may also cause us to change the value we saw in topics in the past. Topics listed here in the HOLD are not necessarily bad, it just means that for the type of software we're building and consulting, there may be better alternatives. There may still be valid reasons to go with those topics in specific situations.
Implementation
We use the
Team
The iits Technology Radar is one of the side projects in the company. It doesn't require full-time involvement. We want the Technology Radar to cover the areas of expertise of the entire company as much as possible. That's why as many representatives from different areas of the company as possible are participating.
Contact Person:
Contributors |
Areas of Expertise |
|---|---|
| Artem Lajko | CloudOps |
| Can Aykin | CloudOps, Security |
| David Becker | Backend, Coding, Database |
| Dmitry Bret | Frontend |
| Emily Reppin | CloudOps |
| Frank Steidinger | Backend, Coding, Frontend |
| Frederik Pietzko | Backend, Coding, Frontend, Method, Pattern |
| Georg Braunbeck | Backend, Coding |
| Igor Ionov | Backend, CI/CD, Coding, Culture, Database, Pattern |
| Jonathan Eschbach | AI |
| Julius Alexander Bainczyk | Frontend, QA |
| Kai Ito | Frontend. |
| Marouane Mhamdi | Backend, CI/CD, Coding, Culture, Frontend, Pattern |
| Peter Ewert | Backend, Method, Pattern |
| Philip Ehnert | AI |
| Mattias Cockburn | CI/CD, CloudOps |
| Robert Wloch | CI/CD, Coding, Culture, Frontend, Method, Pattern, QA |
| Robin Bially | AI, Backend |
| Sebastian Siemens | Backend |
| Sören Schellhoff | Culture, Method, Pattern |
| Tamara Doll | Backend, Frontend, Tools |
| Tim Delbrügger | AI, Culture, Method, Pattern |
| Tobias Américo-Schmidradler | Frontend |
| Tobias Schanz | AI |
| Tolga Akkiraz | Backend |
| Zeljko Bekcic | CI/CD, CloudOps, Coding, IoT, Security |
Homeport AI
The description of the blibs has been polished by using our
The following prompt was used to generate or polish some of the markdown blib descriptions:
Please generate two paragraphs for the above input that can be used as a professional description of a blib in a techradar. If necessary fill missing but valuable information. Try to rephrase I-narrative to “we” and keep some emotional flavor if it was provided. Please highlight in the text a few essential key phrases by inserting “**” directly at the start and end of each such span. Include adjectives in the spans if there is one directly before them.
Each AI generated blib description was reviewed and edited by humans afterwards.