Based on the topic many would have thought that I’m gonna talk about how building software is a marathon, not a sprint. But, that was a good guess, but actually I’m gonna talk about what happens when a marathon is over, and when a software is been launched.
After Deployment:
One of my seniors once told me that they have worked on numerous Softwares that launched and they never touched again until it was time for an update or to rewrite.
Can anyone just imagine what if a marathoner had taken the same approach? They worked really hard and completed the marathon within their goal time, and then just stopped their training. The runner cannot expect the same outcome in his future races as their body goes into a state of disrepair.
The human body is a system that needs constant attention if it’s going to perform well. So does a software system. Once you launch it, and if you don’t continue to maintain and monitor the system, there occurs some malfunctions and performance lacks and as a developer you may not even know it.
Monitor and Maintain:
You know that a runner always strives for a personal best, so does software, it needs to be continually improved. But these improvement/updates aren’t possible if you don’t monitor it and keep yourself in track.
For a marathoner to get better after a race, it’s all about tracking mile split times, setting up some goals and having a good training plan. For software to improve after launch, it needs analytics, logs and a vision to make it better.
So, if you are responsible for launching and maintaining a software think of yourself as a marathoner, ask yourself What is my next goal? How can I improve this system? What things am I gonna do today that will put me in the road to success tomorrow?.
Comment