Recently I read a Reddit post that was posted on the subreddit r/cscareerquestions. It was posted by a junior developer from the U.S, who travelled across the country for his very first job. In the first week, he was given access to the production DB (But why?). With some false judgement from his side, everything went into mayhem. Long story short, the production data was gone...poof, just like that. A hefty price for a mistake from a junior dev. The guy was fired, and the company said they will take legal actions against the fellow.
I am not supporting the junior dev here on his mistake, but in a world, where we celebrate every single minute of success, why don't we ever hear about failure stories much?
Failure is the best teacher in many ways, isn't it?
I like to share my failure story from my very first company, and how I made a database error that cost my company around $1000.
I was working on my very first project back in my first company. Let's say for privacy sake the project I was working on is for a company named X. X is a multi-million company with lots of data at stake every day.
I was allowed to work around their some entity and its cost-related problems. With a lack of understanding or miscommunication from one of my BA (and from my end), I miscalculated a business idea, that leads to an entity getting swapped by yet another entity. result? A total amount loss of $1000, since the original entity, costs more than the new misplaced one. So now the customers who originally chose the old entity gets the cost of the new misplaced one, which is particularly cheap compare to the old one. Thus causing a huge loss in terms of money for X. (This is not the actual gist but for the sake of simplicity let's assume so)
Luckily I understood the problem that I caused and by the time I fixed everything $1000 was registered as a loss.
This was a great lesson that paved the way for my development career, and how to look into a problem twice. That taught me there might be a hidden problem lying somewhere waiting to be discovered. This experience of mine was so helpful when I worked on another project 2 years later for a company Y. They had a database design on firestore, that they were so adamant to implement, even though it was not economical. My past failure helped me to judge the cost implications of that bad design and I was able to show them an alternate design pattern, which helped them reduce the cost without compromising on usability and UX, which I am so proud of.
The same experience helps me whenever I try to integrate cloud services or payment services like the stripe on my projects, and helps me to ask "Is there a much more efficient and cost-effective way"?
So was my mistake a good thing or a bad thing? I don't know the answer to it even now. But I like to see it as a bad mistake with good future implications.
Maybe our failures can shed some light on younger generations. so that they avoid these mistakes when they start their journey. Maybe that's why StackOverflow is so a popular site. It is a collection of questions and mistakes. Right?
Talking of failures, this blog post is an inspiration for this writing. Do check it out.
Comments
Post a Comment