The Beginning: From College to Corporate

Introduction

Let's start with WHY. Why did I choose to write this blog?!? Was I bored on Weekends? Definitely Not! I have always wanted to write a blog related to my field, Software Development. This blog will cover my initial days, how my journey started & some lessons that I learned along the way. So sit back, relax and enjoy the read.

Rewind

I can still remember when the placement season was just around the corner, and we all went into full-on panic mode, cramming like crazy. We wanted a placement so badly — because, honestly, what else were we here for??? All the league matches we played (learning new skills, doing semester assignments just before the deadline, and qualifying semesters without a KT) eventually helped us to play the final match — PLACEMENT — where the real game of life begins!

It was mid-February when a company arrived that felt like a perfect match for me. I’d already developed a genuine interest in software development by then. My journey began in the 4th semester when I started with HTML, CSS, and JavaScript. And let me tell you, it was like an iceberg — a few bits of it floating above the water, but a massive chunk hidden underneath. I started building small projects, like a GYM website, a Food recipe website etc. (Yup, those gems are still hanging out on my GitHub if you're ever curious.)

Then one day, I heard two words that would change everything: Frontend and Backend. I was like, "Wait, what?" So, naturally, as any curious person would, I turned to the fountain of knowledge — YouTube. I watched a few videos that broke it all down for me, and I went on a bit of a binge, watching every video I could find. That’s when I discovered the difference between what the user sees on a website (the Frontend) and what happens behind the scenes (the Backend).

And just like that, I had my “Aha!” moment! It felt like I had just unlocked a hidden level in a game and was hooked. I dove headfirst into both worlds, trying to figure out where my true passion lay. After playing around a bit, I realized I had a love for both, but I was leaning more toward the Backend. There’s just something so satisfying about making the invisible magic happen — the logic, the data handling, the way everything connects seamlessly (or at least, that’s what we aim for!).

Fast forward to the placement process, and there I was, applying to companies that spoke to my love for development. I still remember my interview — nervous, yes, but also super excited. The questions ranged from algorithms to explaining the projects I had worked on (special mention to my Social Media and Crypto Websites, plus a few Open Source contributions!). Thankfully, all those sleepless nights of preparation, debugging, and late-night coding paid off. I got the offer!

Stepping Into the Real World

And that’s how my journey at AppDirect began as a Software Development Engineer Intern. I had been told that we were expected to be in formal attire, so I completely followed the rules. But when I walked through the doors on my first day, I immediately started questioning myself. "Am I the only one dressed like this?" Everyone around me was dressed well, but definitely not in full formal attire. It was my first embarrassing moment on the job — and I couldn’t help but laugh at myself!

Soon after, I had a few inductions planned with different people, and one of them was with the IT team. Oh, that was an exciting moment for me! When I finally saw the laptop assigned to me, I couldn’t believe my eyes — it was a MacBook Pro! I think it’s a dream for every newbie programmer to get into the Apple ecosystem and have that sleek machine to work with. I felt like I had just levelled up!

I remember a site visit was happening where some high-level executives were visiting the branch I was in. Somehow, I ended up bumping into a person named Joe. Before I knew it, I found myself blurting out that I was a bit nervous, wondering if I would be a good fit for the position and whether I could really thrive in the industry. Joe quickly suggested we step into the nearest meeting room, and we did. There, he patiently started explaining a bunch of things to me, beginning with the importance of being proactive.

After all the inductions, my team was finally finalized, and I was introduced to the various services they work on. As a passionate developer, I couldn’t help but feel thrilled when I saw the technology I'd be diving into — Java, Spring Boot, JavaScript, Kotlin, REST, GraphQL, and so much more! It was like walking into a playground filled with all my favourite toys. At first, it was a lot to take in. My brain was trying to connect all the dots from my previous projects to the new technologies I was now working with. But slowly, things started to click. Every day was a chance to learn something new and to grow a little more.

From those first few awkward steps to finally finding my footing, my journey at AppDirect was off to an exciting start. I wasn't a genius coder who could hack into anything, but a newbie with a lot to learn — and I was ready for the adventure ahead.

Navigating Through Challenges: Bugs, Breaks, and Breakthroughs

Oh, the bugs! They’re like uninvited guests that just won’t leave. I still remember the first ticket assigned to me — fixing wildcard bugs in the search functionality. That’s when I truly discovered the art of debugging in larger codebases. I learned how to check logs, analyze stack traces, and dig deeper into the code to find the root cause. Sometimes, you just have to take a step back, breathe, and really understand why the bug exists in the first place and what exactly went wrong. Each bug felt like a puzzle, and every time I solved one, it was a small victory, a breakthrough that taught me a new lesson. I'd love to express my gratitude to the senior programmers who taught me these things.

But it wasn't always smooth sailing. There were moments when I seriously doubted myself. Imposter syndrome hit hard. I’d look around at my colleagues, who seemed to have it all figured out and wonder if I’d ever get there. But over time, I realized that even the most experienced developers have days when they feel stuck or unsure. The trick is to keep pushing forward, keep asking questions, and not be afraid to fail. Because, in the end, every mistake is just another step towards getting better.

What I’ve Learned (So Far)

Stay Curious and Keep Learning: No matter how much you think you know, there’s always more to discover. In software development, every day is a chance to learn something new.

Don’t Be Afraid to Ask for Help: I used to think that asking for help was a sign of weakness, but I’ve learned it’s actually a sign of strength. It shows you’re open to learning and growing. That said, I still believe it's important to give the problem your best shot before reaching out for help.

Observe Experienced Developers: Pay attention to how experienced developers approach problems and tackle challenges. There's a lot to learn just by watching and picking up on their methods and tricks.

Looking Forward: What’s Next?

So, here I am, 180 days in, still learning, still growing, and still excited about what’s to come. Now that I've been promoted to Associate Software Development Engineer, I feel like the journey has just begun, and I’m ready for all the challenges, adventures, and surprises the next coming days will bring. If you’re just starting your own journey, I hope this gives you a glimpse of what’s ahead — the ups, the downs, and all the incredible moments in between.

Stay curious, keep coding, and never stop dreaming. And most importantly, enjoy the ride!