BackEnd Development

This blog is a reflection of my journey into backend development using ASP.NET. It’s raw, real, and written from the trenches.

How It Started.
I didn’t start out as a backend developer. I began as a frontend enthusiast, driven by a bold ambition: to design and develop the most beautiful user interfaces the world had ever seen. Frontend development is art. The interfaces you create aren’t just for your eyes—they’re for the eyes of the clients who will use the application. As an artist, you need a keen eye for detail and design to experience the ‘high’—the gratification—that comes from crafting something truly elegant.

After building several frontend projects from scratch, learning the ins and outs, and discovering how to cleverly amuse clients with subtle design choices, a realization hit me: What is design without functionality and data? It’s flesh and bones without soul and mind.

That’s when I felt compelled to begin my backend journey. It wasn’t a shift—it was a continuation.

The Shift
My backend journey actually began with a search for the right framework. I initially explored Spring and Spring Boot, intrigued by their structure—especially since I was already familiar with Java syntax and semantics. But something didn’t sit right. My gut just didn’t vibe with Spring Boot, and I found myself drifting toward other options.

It felt like diving into a vast sea of possibilities. Where others might have felt overwhelmed by the abundance of choices, I saw opportunity. I wasn’t shy about experimenting. I tried out a range of frameworks—Django, Node.js, Firebase, and of course, ASP.NET.

After kissing many frogs, my heart was finally won over by a princess named ASP.NET. What can I say? I like what I like. ASP.NET had the feel I was searching for, and now, two years later, we’re happily married.

The Grind
Well, it’s been quite the ride with software development. So far, so good—except I’m teetering on the edge of a mental breakdown! Lord have mercy. Anyway, no biggie—I’m hanging in there. Taking each day as it comes, breaking down the chaos into manageable chunks. They say what doesn’t kill you makes you stronger, right? But if it ends up costing you an arm and a leg, you’ve got to ask yourself what kind of twisted optimism led you there.

All jokes aside though, I’m genuinely proud of how far I’ve come. If someone accidentally started clapping, I’d probably start thanking everyone who’s helped me along this wild journey toward my never-ending, never-quite-reaching dreams. I’ll get there eventually—hopefully soon—but ASP.NET isn’t exactly rolling out the red carpet. Anyway, I’m a certified crybaby, so I could complain all day about my ordeals. But let me get into the nitty-gritty of the problems now.

I’m no rookie when it comes to the ASP.NET framework now—I’ve built several working RESTful APIs with C#. Feel free to consult my résumé, where I’ve audaciously showcased what I can do with the framework. Such boastfulness. Such high-stepping. Honestly, reaching those heights was a massive relief. And truth be told, I’m actually a pretty humble person—not even that brave.

I remember vividly: it took blood, sweat, and sheer resilience to silence the impostor syndrome and all those inner demons screaming that I wasn’t good enough. Only then could I start grasping the concepts and best practices needed to tackle the challenges that came my way. The mental and emotional turmoil—from learning how to craft interfaces and implement their functions within respective classes, to building controllers that produce sleek, well-structured API outputs—was intense. I figured out how to connect MariaDB databases to my project, and even pushed further into JWT authentication to ensure secure user access.

Like any good honeymoon, my early days with ASP.NET were filled with excitement and discovery. Everything felt new, promising, and full of potential. But as the honeymoon phase faded, reality set in—and backend development revealed its true complexity.

Backend development isn’t just challenging—it’s humbling. There are still major topics I’ve yet to fully explore: CDNs, microservices, webhooks, sharding, caching, message queuing, and probably a dozen others I haven’t even named yet. But despite the steep learning curve, it’s a journey worth indulging. Every new concept is another step toward mastery—and I’m here for the long haul.

What’s next?
I’m still learning, and that’s the best part. ASP.NET has opened up a whole new world of possibilities. I’m no longer just a frontend developer—I’m becoming a full-stack creator. My goal now is to build apps that are not only beautiful on the outside but powerful on the inside. And this blog is just the beginning of documenting that journey. If you’re on a similar path or just curious about backend development, let’s connect. Drop a comment or reach out—I’d love to hear your story.