Decaying Solutions
Senior Application Developer and Full Stack Engineer at Thoughtworks with almost a decade of experience working primarily as a Backend & DevOps Engineer. I've worked on Ruby & C# projects and am currently working on a Python one. I am an AWS Certified Solutions Architect and an Oracle Certified Cloud Infrastructure Architect at an Associate level. I also have reasonable experience working on GCP, primarily with Google Kubernetes Engine.
I'm also an aspiring public speaker who likes to give talks on soft skills and tech.
I also write blogs on various psychological aspects of work primarily to improve teamwork & interpersonal skills.
A few months ago, I changed my doorbell.
While it was still functioning, its volume had become really low. After changing it, I noticed how it was loud enough to hear from anywhere in the house even when I closed my room door during work meetings.
This was significant because my family had spent many hours over the years arguing between ourselves because of the doorbell. Several people, including every family member, had spent a lot of time ringing the doorbell repeatedly because the people inside couldn't hear the feeble bell.
So why didn't we replace it earlier? Even though it no longer served its purpose effectively, we didn't replace it. After all, it was still working to some extent. So we inadvertently chose to suffer rather than fix the problem.
How many times have we done this in our personal and professional lives, where we prefer to put up with a worsening situation rather than address it, just because we believe that we already have a solution in place.
The moral of my story is that to look for such problems/pain points before you spend years suffering because of it. And once you realise that there is one, address them soon and your future self will thank you.
