My Journey as a Software Engineer

I mean, where the 'frell' should I really even start 🤔?

So here we are—my very first blog post! 🎉 I could start by telling you how I’ve always dreamed of being a software engineer since I was a wide-eyed child, doodling on the back of napkins with visions of code dancing in my head. But let’s be real for a moment: my journey into this world was less of a graceful leap and more of a lifecheck—a realization that led me into a field I’ve come to learn and love over the years, where problem-solving and creativity collide in ways I never expected.

I stumbled into software engineering fueled by my unwavering love for science and problem-solving because what better way to spend your days than turning abstract concepts into tangible applications that occasionally, and I do mean occasionally, function as intended? It’s like being a magician, only instead of pulling rabbits out of hats, I’m pulling logical solutions out of thin air and hoping I don’t accidentally conjure a bug that will haunt me for days.

Now, here's the plot twist: I actually wanted to be a pharmacist! My love for science ran so deep that I got admitted not once, but twice, to study pharmacy. Yep, I was ready to don that white coat and whip up some life-saving potions. But fate had other plans, and here I am, writing code instead of prescriptions. So, while I didn’t end up mixing chemicals in a lab, I get to tinker with logic and algorithms, which—let’s be honest—is just as much of a science experiment.

Coding: The Modern-Day Alchemy (Minus the Gold)

People think coding is some mystical art, like you type a few cryptic symbols and—poof!—the app of your dreams appears. The reality? Coding is like trying to fix a car while the engine is still running and someone's constantly throwing new parts at you. Half the time, I'm breaking things just to figure out why they broke (lol just kidding). Actually half the time, I'm deep in thought, scoping out potential solutions and dissecting problems to understand where things went awry. The other half? Discussing with clients and designing solutions that (hopefully) address their needs. Of course, sometimes it all comes together seamlessly—and other times it doesn't.

But hey, when it works, it feels like alchemy. Suddenly, all that chaos turns into something useful. You push a button and things actually happen. It's like pulling off the ultimate life hack… except instead of impressing your friends, you're getting a machine to do what it's supposed to do to solve a real life problem.

From "Hello, World" to "Why is This On Fire?"

Ah, the good ol' "Hello, World!"—the software engineer's baby steps into this wild, unforgiving world. The first time you see those words printed on the screen, you think, "Wow, I'm basically a genius." Fast forward a few months, and you're staring at your code thinking, "Why is this entire thing on fire?"

Somewhere between those two moments, you learn that coding is about making slightly fewer mistakes each time. Now, instead of simple scripts, I'm wrangling complex apps—stuff that handles payments, systems used by thousands of people every day, and deals with enough data to make your head spin. If "Hello, World!" was child's play, this stuff is like juggling chainsaws while riding a unicycle.

Someone Has to Tell the Truth

Look, this blog isn't here to sell you a dream. It's not going to be one of those motivational "You can code your way to the moon!" kind of spaces. Nope. This is going to be a mix of tech tips, sarcastic rants, and the occasional dose of reality. You'll get:

• Tech tips: Actual useful stuff. Think debugging hacks and tools that make life easier, not those "learn to code in 5 days" gimmicks.
• Project breakdowns: I'll take you behind the scenes of what I'm building. APIs, integrations, and yes, those times when nothing works and everything is pain.
• Code Fails: Yes, I screw up—often. I'll share my biggest facepalm moments, because if you can't laugh at your own mistakes, what's the point?
• Pep talks (with a twist): You'll get motivation, but the honest kind. The "Yeah, this sucks right now, but you'll figure it out" sort of pep talks.

What's Next?

So, what's next? I'll be posting regularly (or as regularly as one can between coffee refills and debugging nightmares). Stick around if you want to learn, laugh, and maybe avoid a few pitfalls in your own coding journey.Trust me, you'll want to hear the stories I've got lined up.

Until then, keep coding, stay caffeinated, and don't forget to laugh at your code — it's laughing at you, too.

😎Comments section coming soon! Go on buy me a coffee to drink whilst coding that for ya!!