A Year of Growth: My Journey Into Software Development
I joined Adept in October 2023 as an attaché from Riara University. Truthfully, I walked in wrestling with a serious case of the unknowns. Every practical assumption I had was instantly called into question: Would they have a strict suit-and-tie dress code? Would I need to abandon my long hair? Above all, the most crippling thought was the doubt: Am I even good enough? Everyone else seemed to have years of experience under their belt. If overthinking was Michael Jordan, then imposter syndrome was Scottie Pippen and together they were running up an embarrassingly high score on my confidence.
The Culture Code: Building Trust, Not Borders
As is often the case in life, the reality was nowhere near as bad as the fear I had built up. In fact, it was infinitely better. From day one, I loved the environment. It didn’t feel like I was back in a restrictive academic or institutional setting, which was my greatest fear. Instead, I was treated like a professional, entrusted to make decisions with guidance, and judged strictly on performance and the desire to improve. This culture, where trust replaces micromanagement, was foundational to my rapid growth.
The Agile Team: More Than Just Code
In any high-stakes, communal endeavor like software development, the quality of your experience is tremendously dependent on your team. I couldn't have been luckier. My colleagues demanded excellence without ever being overwhelming. They gave me ownership and responsibility instead of drip-feeding tasks, a true accelerator for a young developer. Most importantly, they never made me feel like I was out of my depth.
A special recognition is owed to my boss, Fuji. His approach to leadership is my personal benchmark: demanding the best, providing clear direction, and fostering confidence. If I ever find myself in a leadership position, I owe it to my team to be to them what Fuji has been to me.
Diving Deep: My First Software Development Project
Adept, being a relatively young and agile company in the software development space, meant that significant responsibility fell onto my shoulders, a challenge I embraced. My very first project as an attaché was a children’s game designed to help with number recognition. Balloons with various numbers floated up the screen, and the child had to pop the balloon corresponding to a spoken number.
I was given a two-week deadline and immediately thought, “I’m finished! Where do I even begin the development lifecycle?” Computer science degrees, while theoretically robust, often leave graduates with minimal practical programming experience. That project forced me out of my theoretical comfort zone and provided massive real-world experience in project scoping, iteration, and deployment.
Off the Bench and Into the Game
My attachment led to an internship, and six months later, I was offered full-time employment. Fast forward one year since that initial attachment, and my development trajectory has been exponential. I’ve gone from building a simple game to spearheading multiple software development projects, assisting with technical interviews, and even leading team-building sessions (we went bowling, and my score was atrocious, but that’s a story for another day!).
I am profoundly grateful to have this breadth of experience only one year into my career. While working for a larger, more established company often comes with better-known perks, the common downside is the institutional "spoon-feeding" that happens early in one's career. You end up sitting on the bench, cheering others on. Who dreams of that ? Not me.
I am not here to hand out towels after someone else has been subbed off. I am in the field: coding, contributing, learning, and growing. There is no greater professional satisfaction than being a vital, active part of the solution, especially in the fast-paced world of software development. There is nowhere else I'd rather be.