Hello, World! 👋

I’m Omar H.Ajmi, a software engineer based in France 🇫🇷.

I’ve spent a good part of my professional life building software, solving problems, untangling complexity, and occasionally wondering how on earth a perfectly innocent change managed to break something that had been working flawlessly for three years. You know the drill. 😅

But somewhere between the debugging sessions, the elegant solutions, the questionable variable names, and those wonderful moments when everything finally clicks, I realised something:

I don’t just enjoy writing software. I genuinely love the craft of it.

And that’s what this little corner of the internet is about.

🛠️ More than making things work

There’s a difference between writing code that works and building software that feels right.

It’s in the small things: a well-named function, an interface that makes sense without a manual, a solution that’s simpler than the problem first suggested, or a thoughtful refactoring that makes the next person’s day just a little easier.

It’s knowing when to reach for a clever solution — and, perhaps more importantly, when to resist the temptation.

Because let’s be honest: we software engineers occasionally have a remarkable talent for turning a three-line problem into a distributed system. Sometimes, the best architecture is the one you don’t have to explain with seventeen diagrams. 😉

For me, craftsmanship is about caring. Caring about the details, the people who will use what we build, the people who will maintain it, and the future version of ourselves who will inevitably revisit that code at an inconvenient hour.

It’s about remaining curious, questioning assumptions, learning from mistakes, and never becoming so experienced that we stop being beginners at something new.

Experience teaches you a lot. Humility teaches you to keep learning.

And the craft? The craft keeps things interesting. ❤️

🧠 Always a student, occasionally a wizard

Software engineering is a wonderfully humbling profession.

No matter how much you know, there’s always another concept to explore, another tool to understand, another paradigm to question, or another bug to remind you that computers are extremely literal machines with absolutely no appreciation for your intentions.

I’ve learned that some of the most valuable lessons don’t come from getting everything right. They come from the things that don’t work, the assumptions that fall apart, the approaches that turn out to be terrible ideas, and the moments when someone else shows you a better way.

That’s why I believe in staying curious.

I want to keep improving how I design systems, write code, approach problems, share knowledge, and think about technology. Not because there’s some finish line where we finally become complete engineers, but because getting better at something you love is part of the joy.

There is always more to discover. And honestly, how lucky are we to work in a field where learning never really ends? 🚀

✍️ So, why this blog?

Because knowledge is too useful to keep locked away in the back of your brain.

Over the years, we collect little discoveries: a technique that saves hours, an architectural decision that finally makes sense, a subtle language feature, a hard-earned lesson from production, or a tiny trick that makes an otherwise frustrating problem surprisingly simple.

Some lessons take years to learn. Others arrive at 2 a.m., somewhere between a stack trace and a questionable amount of coffee. ☕

Either way, I don’t want those lessons to disappear into the void.

This blog is my attempt to capture them.

You’ll find things I’ve learned, ideas I’ve explored, problems I’ve solved, mistakes I’ve made, and opinions that may evolve as I learn more. Some articles might dive into the technical details; others might reflect on software design, engineering culture, tools, or the philosophy behind building good software.

I’m not here to pretend I have all the answers. I certainly don’t.

I’m here to share what I discover, explain what I understand, and hopefully make someone else’s journey a little easier along the way.

And if writing forces me to understand a topic more deeply, question my own assumptions, or discover the holes in my understanding, even better. Teaching is a rather effective way of discovering what you don’t know. 😄

The goal is simple: help others, help myself, and leave things a little better than I found them.

🌍 A small contribution to a very big world

The internet is one of humanity’s most extraordinary collaborative creations.

Somewhere out there, a developer has written a blog post that will save another developer an entire afternoon. Someone has published an open-source library that makes a difficult task accessible. Someone has explained a confusing concept so clearly that a stranger halfway across the world finally understands it.

Often, we’ll never know who those people are.

We benefit from their generosity without ever meeting them, and we carry their work forward in ways they may never see.

I find something beautiful in that.

So this blog is also my small way of giving something back. Not with the grand illusion that a few articles will change the entire world, but with the belief that small contributions matter.

If something I write helps someone solve a problem, understand a concept, make a better technical decision, or simply feel a little less alone while wrestling with a stubborn bug, then it has served its purpose.

And perhaps, years from now, someone will stumble upon one of these articles, find something useful in it, and carry that knowledge a little further.

That would be wonderful.

I’d like this blog to be more than a collection of pages on a domain I happen to own. I’d like it to be a trace of my journey: what I learned, what I cared about, how I thought, and how those things changed over time.

A little digital footprint. A record of curiosity. A contribution, however modest, to the collective knowledge that makes our craft possible.

We don’t get to choose how far our work travels. We can choose to put something worthwhile out there.

☕ One article at a time

So, here we are. A fresh page, a blank canvas, and an unreasonable number of things left to learn.

I’ll try to write regularly, keep things honest, favour substance over noise, and remember that behind every technical problem is an opportunity to understand something a little better.

Expect practical lessons, technical explorations, occasional rabbit holes, strong opinions held loosely, and perhaps the occasional reminder that deleting code can be just as satisfying as writing it.

No guru act. No pretending every lesson was obvious all along. No need to turn every thought into a revolutionary new methodology.

Just an engineer who loves the craft, remains curious about the world, and wants to share a little of what the journey teaches along the way.

If you’re another engineer, a curious learner, or simply someone who enjoys understanding how things work, you’re very welcome here.

Make yourself at home. 🏡

And if you happen to learn something along the way, even better.

Here’s to building things thoughtfully, learning relentlessly, sharing generously, and leaving the world with a little more knowledge than we found it.

Happy building. 💻❤️

— Omar, somewhere in France 🇫🇷