Our tech radar is highly motivated by ThoughtWork’s vision of the technology radar, which is a visual document of industry changes we find interesting as well as of what tech we have trialed and adopted in our company. The output goal of our tech radar is to create publications on what tech we see in our projects. As of the time of this writing, this will be our Volume 1 of our tech radar.

How to participate?

We encourage our engineers to create a post of any interesting tech that they believe might bring value to the company at our **#learning-topics forum channel on our company Discord.** If you believe the tech is worth having a deeper look at or an RFC (Request For Comment) to be implemented in a project, just ping monotykamary#6285 or thanh#0605, and we’ll set up roles and brief you in the process to document and kickstart the journey for the new tech. For more details, check out our documentation:

Process

Roles

What is the Tech Radar about?

The visual document represents our opinions on tech and what we find useful for our use cases. Similar to ThoughtWork’s vision of the tech radar, our radar program consists of:

Quadrants

The quadrants consist of:

• Languages and Frameworks, e.g., Erlang, Svelte, R
• Techniques, e.g., new design technique, software structure, microservices architect.
• Tools, e.g., editors, databases, software development tools.
• Platforms, e.g., things provided by others that we build software on top like Vault, Istio, JupyterLab.

Rings

Our radar has four rings, start from the middle.

• Adopt: These are technologies we use in our projects when appropriate. They are also tech we believe the industry should strongly adopt.
• Trial: These are technologies worth pursuing and may be used in projects that aren’t afraid to bring in new tech.
• Assess: These are tech items we believe that are worth exploring and researching on, so that we understand what impact it may have in our company.
• Hold: These are technologies in our watch list, but unsure whether it’s worth delving deeper.