The goal of our LimeSoda Tech Radar is to give an overview to our employees, clients, partners and whoever else it might concern which languages, frameworks, tools, patterns and platforms/services we are using.
Note that we don't list everything which we are using. When a "blip" (i.e.: an item) is listed here:
- it has a certain importance for us,
- we want to build awareness in our team for it (e.g. a new tool which will be used in every team), or
- we just think it's worth for everybody to look into it.
In our February 2019 edition, we decided to add more "basic" entries than you might find in other Tech Radars. We found the Tech Radar is good for giving new and potential colleagues an overview how much our stack matches what they know, so it make sense to add operating systems and the like to the mix.
Also important: we don't think that the tools, services etc. which we are using are the only "right" ones to use. They are just the ones we are working with for now. They might change in the future. Always use the right tools for the right job.
The tech radar categorizes blips on two levels: qudarants and stages (explained below). Often, it's hard to clarify where a blip should go because multiple quadrants / stages might apply. In this case, we put them were we think they belong best.
The four quadrants are:
- Languages and Frameworks: programming languages, frameworks and software which are the foundation for our projects. We usem together with our platforms and tools to realise websites, webshops, web apps, social media content, videos etc.
- Techniques: an umbrella term for best practices in our workflow, think methods and patterns. In the first iteration of our Tech Radar, we only mentioned a few of them but if you are interested, we might elaborate more in this area.
- Platforms & Services: platforms and services which are the base for our work. For the February 2019 edition, we decided to move some blips from "Tools" to "Platforms & Services". Social media and interaction is a big and important part of our company culture and team. So we deemed it best to view our communication and some of our main workflow tools as platforms which are the base for our work.
- Tools: all kinds of software which help us being more productive, quicker and better.
Stages of adoption
Second, there are different phases in the usage lifecycle of a blip. At the beginning, you might hear about some new fancy platform, technique, ... coming up. You are not sure yet what to make of it, but a late time you might decide to have a closer look. You might decide that you want to use it more (or that it's just not right for you). If you establish a platform, technique, ... in your company, you might decide after some time that it's time to let go and move on to its successor.
This lifecycle is represented by the second categorization. Originally called "rings", we refer to them as "stages of adoption".
The four stages of adoption are:
- Adopt we actively encourage the use of these blips in our daily work.
- Trial: we are using these blips in real projects or evaluate them closely for usage in a wide range of our projects. Also, blips might be in this stage if we are very sure we will adopt them but they are still very new.
- Assess: blips which we find interesting and often are already investigating. We are trying to find out if they are the best alternative, should be used more often and become part of our adoped stack.
- Hold: in this stage, we either (a) have used a blip before and after having being a good blip for us, we moved an to a new/better solution or (b) have assessed a blip and found it to not be suitable for us.
If you have any more questions, remarks, ... on our technology radar or blips, please contact us!
Our technology radar is based on AOEs project. Thank you very much for open sourcing this, AOE!