Do you
have a highly motivated DevOps team, available 24/7 to monitor and react in the event of a problem?
Sometimes, it is important to know how to resist fragile technological trends: Simplicity is strength.
5. Documentation
I hear many gurus say that documentation is the old world. There is a new world, in which documentation is useless and slows down progress.
So let's set the record straight.
YES, documentation is a thankless task.
YES, documentation makes the BUILD of a project a little heavier.
But in the RUN phase, if your project lasts several years, that is to say if the developers change, the absence of documentation will be a real obstacle to maintenance and will make developments very risky.
If you do a POC, you will do without documentation without any problem, on the other hand if you carry out a business project that is at least a little complex, document it to ensure its future .
6. Tests
Automate the tests, ensure substantial coverage with real functional and technical tests.
Define a governance for taking into account developments and anomalies and equip this governance.
You already know all this, I'm afraid I won't teach you anything on this subject, the difficulty lies in the action: "Just do it" .
7. Developments, MCS and updates
An application must regularly perform a gymnastics session to update its libraries and software. This update is sometimes vital, particularly in the context of security alerts, it is often optional, however ...
It is therefore advisable to regularly update the application stack to avoid finding yourself faced with update dead ends, or even unconsidered risks.
Software is a living organic system, it must be updated to promote developments.
The versions of underlying libraries and software must be chosen to be consistent, coherent and sustainable. LTS (Long-Term Support) versions must be preferred, end-of-life (EOL) dates must be followed. This monitoring and management will be the responsibility of committees dedicated to MCS or Maintenance in Safety Condition.
Of course, not all developments are attributable to technology and certain regulatory changes require modifying the code at the risk of creating functional obsolescence. It is therefore essential to extend the lifespan of a software to create modules capable of supporting both technical and functional developments.
Convictions
Building a functionally complex application will be switzerland telegram data on which it is based is simple and mastered .
This seems like a truism, yet it is clear that too many functionally rich business applications start on experimental technology bases, poorly understood by developers and operators.
Let us mention micro-services which are very fashionable and remain, unfortunately, misunderstood by most teams. So they backfire like a boomerang against those who use them and knock out projects.
Boileau said in the 17th century,
" What is well designed is clearly stated,
And the words to say it come easily."
The same is true in software development.
If the functional and technological statements are not clear, it is because problems will not be long in coming.
Obsolescence is programmed, sustainability is thought about, planned.
And simplicity remains a key that is too often ignored to achieve it.
Dare to be simple, Dare to be efficient.