In recent years, companies have been in tension in the field of recruitment. Finding competent people is quite complicated. When I talk about skills, I am not only talking about technical skills, but also about know-how. We will never replace experience and practice. The likelihood of simplicity and speed of creating infrastructures with these languages introduces a new dimension of complexity and risk, opening the door to a "new form of technical debt".
The proliferation of tutorials, accessible and AI-generated code loan data has transformed the landscape of development via infrastructure as code. We don’t realize that using a module Terraformor role Ansiblefound on the internet without fully understanding how it works can be dangerous in terms of security, performance and resilience. I’m not even talking about AI.
The lack of real professionals
By deliberately choosing not to use architecture and security specialists , you can produce heavy technical debts. These professionals are essential, because in their absence bad decisions can be made. And this kind of mistake right from the beginning of the project can lead to a real “Bérézina”. Deploying an application on a Kubernetes cluster does not make you an expert in this kind of solution!
Bad technical choices
Another mistake: wanting to use a new or unknown technology. This type of choice is often made to follow the trend, to learn a new technology, to try to meet a need. Whatever the source of your decision, do not forget that you are setting foot in uncharted territory. Even if you have attended a great demo, do not forget that you will then have to be able to use it in real conditions. You will have to ensure the upskilling of all your teams to ensure maintenance in operational condition.
To avoid this kind of mistake, try to answer these questions:
How long has this product been around? I've noticed that it takes 2-3 years for a technology to start maturing.
Is this tool used by a large number of customers?
Are resources easy to find? A well-documented and cited tool will save you a lot of searching.
How many people are involved in its development? A foundation is safer than a single developer.
Do I have enough profiles who know this technology?
More classic solutions?
Lack of consistency
Lack of automation and reliance on solutions found on the internet can lead to the creation of so-called “ snowflake servers ↗ ”. Having multiple such servers contributes to increasing technical debt. Managing, updating, and troubleshooting these servers requires specialized knowledge and manual effort. Inconsistencies between servers can lead to unexpected behavior, complicate disaster recovery, and slow down the entire delivery process.
- Board index
- All times are UTC
- Delete cookies
- Contact us