Sharing Story of My Former Team Lead
Tags: devjournal, writing
Published: 2023-02-09 02:31:42


![Documentation](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hzhggxq28pj3lkcom055.jpg)

Hello everyone, i just wanna share my thoughts about my ex former team leader in my current company. This story is about what I felt as a Junior Backend Developer when he led the team. 

## The Story
- I feel my leader is a kind of a protector for developers. For the real example, he always makes sure the feature that will be developed is clear, very detailed, and easy to understand. If the feature is not ready or the requirement is still ambiguous, he won’t give that feature to the dev. Even though there is only a little mistake on the UI, my lead asks the Business Process Analyst (BPA) or the UI Team to fix it first. 

- One day, the users ask for an additional feature after going live. They ask the estimation time to develop is a maximum of only 2-3 working days. I know that  3 days is more than enough but my leader is mad and of course disagrees. My leader told me that at least the team needs 1 week to develop. I don’t know exactly the reason, but after that i feel safe and more comfortable when he leads the team.

- Fyi, when i joined the team, i was a fresh graduate that didn't have much experience about BE development. So sometimes I don't know what I should do to solve my work problem. And again, my leader is very welcome about that. For only 1 year, I worked with him, I feel my experience in BE development is growing exponentially. Hahaha. I learned from him about the clean code, the simple query, the optimum query, and much more. I feel empowered.


- Okay, for this section, it may not sound like it doesn't make sense at all, but it was real. My leader can fix bugs as fast as you blink your eyes. I mean, if the Quality Assurance team finds a bug and tells me to check what's the problem, maybe I need more than 2 hours to only know the root causes (only know the problem, not know how to fix it). But, magically, he only needs maybe like 10 minutes to fix the bugs. Amazing!.

## Why do I respect him so much?

- He spent time helping with all the work, not only development but also fixing bugs, answering BPA questions, etc even when one of his parents died (first thing first, I share this with all my respect to him). His commitment and dedication for the team is beyond my expectation. 
- A simple behavior like answering my chat after working hours, even on saturday or sunday. For some people it seems not polite to chat, but he didn't mind at all just to make sure I didn't have any technical issues.
- He always appreciates, says sorry, and thank you, three magic words that can make a big difference. It really changed the culture of the team so we all felt safe, enjoyed, and happy all the time even though going through hard times.
- His guidance, support, and mentorship have been instrumental in shaping my professional development career and I am truly grateful for the opportunities he provided me with.

And finally we can only just say thank you, thank you very much for the lessons we learned and the memories we made while working with you. I wish you all the best in your future endeavors and I hope our paths cross again in the future. 


<center> **_The One And Only Koh/Mr/Pak Ronny_** </center>

![Ko Ronny Teams Meeting](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ow87gkfnkyn1ybhcyk1d.jpeg)

If you have another story with Ko Ronny, feel free to share your experience in the comment section below.