Just three months into my coding journey, I transitioned from a support engineer to a developer role. I secured my place in the prestigious R&D team. This marked the beginning of a transformative phase, introducing me to my first mentor, RP.
This move to a developer role set the stage for a significant evolution in my coding journey. I felt valued and pleased that my eagerness to learn and dedicated work ethic captured the team’s attention. Moreover, I had an incredible opportunity – to work alongside a programming guru. I vividly recall my excitement about moving into another room and becoming part of the R&D team. We were now five developers, with me being the most junior. My shift to the R&D team not only changed physical space but also shifted dynamics. We decided to symbolize our collaborative spirit by arranging our desks in a circle. I was thinking: “We were like the Knights of the round table.“.
RP was present when the first line of code for our application was written. He seemed to know everything (at least that’s what I thought), and he was (and still is) passionate about programming and delivering state-of-the-art software. A true software craftsman. My fear of EDI had vanished. I developed a completely different mindset, starting to form a new goal – “When I grow up, I want to be just like RP!”.
RP’s guidance and insights played a crucial role in shaping my coding philosophy. Design Patterns, once relegated to theoretical musings in university lectures, began to hold practical significance under RP’s mentorship. Singletons, decorators, and builders were no longer mere exam fodder. They transformed into powerful tools in my coding arsenal.
Despite being the most junior developer on the team, RP treated me with respect. Whenever I didn’t understand something (multiple times a day at that point!), he came over to my desk to help me navigate the issue. He always avoided providing direct solutions. Instead, he guided me step by step, allowing me to gain hands-on experience. @RP – if you read this, thank you for your patience!
Recognizing my newfound interest, RP recommended a transformative read – “Design Patterns: Elements of Reusable Object-Oriented Software” by the Gang of Four (GoF). This book opened my eyes to the profound impact of design patterns on software development. I finally understood not just how to use them but, more importantly, why. I transitioned from a passive learner to an evangelist of design patterns.
RP’s role in my journey went beyond imparting technical knowledge. His mentorship created an environment where questions were encouraged, challenges were met with solutions, and learning became a collaborative endeavor. Our fast connection became the conduit for a wealth of knowledge. I was always thankful to have him around as a guide and a source of inspiration. There’s a saying: “Be the senior you needed when you were a junior.“. I was fortunate to have RP as my mentor and aspired to be the senior I had for my fellow colleagues as I progressed in my career.
My evolution from a novice support engineer to an actual developer was not only marked by technical growth but also by the invaluable lessons learned along the way. Embracing my mentor’s guidance proved to be a cornerstone in navigating the complexities of coding. Recognizing the significance of Design Patterns, I transformed from a passive learner to an advocate. I soon realised that identifying a mentor, building a strong connection, and maintaining a perpetual hunger for learning emerged as essential components of my sustained growth.
The world of IT is dynamic and ever-changing. The understanding that there is no end to learning is a fundamental truth. As I advanced in my career, irrespective of the role I held, I consistently sought mentorship and maintained an open mindset, placing a strong emphasis on continuous learning.