Menu
Michael B., Back-End Developer |
October 29, 2024
The Start of My Journey
My journey began when I first joined Lexcode, the company that introduced me to the world of becoming a Python developer specializing in natural language processing. Like many new developers, I wasn’t skilled enough to build my own backend application or even write a single line of code confidently, so my colleagues and I underwent rigorous training that opened a lot of opportunities for me to learn.
From there, I was immersed in different company projects like TransCreation, the Work Automation System, DFM, and Lexy, a web application that, at that time, was just starting out as a new project assigned to our team. Each new task was a stepping stone that pushed me to grow in unexpected ways. As one of the pioneering members of these efforts, I found myself realizing that the skills I was building would open countless doors for my future career.
Facing Setbacks and Challenges
However, things didn’t stay easy. Over time, many of my colleagues, who had become close friends and mentors, had to part ways for personal and professional reasons. This left me in a state of uncertainty, wondering whether I should continue on my own and face this professional dilemma.
Life, as we know, isn’t always butterflies and rainbows. Things became even more challenging when I was involved in a motorcycle accident, and at the same time, my father’s heart condition worsened. It was a difficult period that put a pause on my momentum. I found myself at a low point, struggling to balance both personal and professional hardships, unsure if I could handle it all.
But one thing was clear: I had no choice but to push through. I had to step up one way or another. And so, I did. I took on the responsibilities that had been shared by others and learned the ins and outs of the project I took care of. This forced me to dive deep and develop skills I didn’t know I was capable of.
As new team members came and the codebase continued to grow, I found myself with more responsibilities than ever before. I realized that I needed to take things more seriously. The bigger the project became, the more essential it was to communicate effectively, implement best practices, and ensure that our code was not only functional but also sustainable for future developers.
Learning became my top priority during this time. I focused on mastering the development, deployment, and management of our codebase and server independently. Writing clean, descriptive codes was essential; it wasn’t just about completing tasks anymore but about ensuring that other developers could easily understand and build upon my work. This approach not only helped me grow as a developer but also allowed our team to work more productively and collaboratively.
Over time, I began to see the impact my contributions had on other teams. The backend systems I helped create significantly boosted productivity for automating tasks and accelerated processes. The Lexy project was gaining substantial momentum, and it was rewarding to know that my code had become the backbone of something much bigger than me.
The Journey That Shaped Me
Looking back on this journey, I realized that the challenges I faced were not just obstacles but vital components of my growth as a developer. What began as a challenge turned into an incredible learning experience. I had gone from feeling unsure about my path to recognizing that I had the skills, knowledge, and resilience to succeed. More importantly, I discovered a passion for backend development that I hadn’t fully realized before.
As I write this article today, Lexy has officially been announced and was recently launched yesterday by Mr. Ham, our CEO, during our company’s weekly Thumbs-Up Talk. I felt pure satisfaction knowing that I had taken this long journey, and I can say that I am one of the proudest developers to finish this project. I realized that it is not the technical aspects I’ve learned or the skills I’ve honed that made me love being a backend developer, but the journey it took to become one.
