Not the kind that works today and breaks tomorrow. The kind that a team inherits three years later and says — whoever built this, thought about us.
I didn't start with a career plan. I started with a question: why does this system work? Not how to use it — why it's built this way. What decisions led here. What trade-offs someone made at 2 AM that I'm now living with.
I completed my Bachelor's in Networks & Telecommunications through a work-study program as a systems administrator. But early on, I stopped at simply operating systems. I wanted to understand them deeply — restructure them, make them more resilient.
My days were split between classrooms and server rooms. I deployed monitoring solutions that could see what humans couldn't. I designed security architectures that assumed breach, not prevention.
Every infrastructure is a choice. Every choice has consequences that outlast the person who made it.
Now pursuing a Master's in Advanced Information Systems, I lead a technology FabLab. I experiment, prototype, design environments where learning and building are the same thing.
This feeds both my professional practice and personal research — automation, cloud-native architectures, zero-trust security. Always with the same question: will this still make sense in five years?
Theory is comfortable. Production is honest. These are systems I've built, broken, and rebuilt — each one a lesson in what matters when things go wrong at 3 AM.
The projects that define you aren't on your résumé. They're the ones you build at midnight because you can't stop thinking about the problem.
I started writing because I couldn't find the explanations I needed when learning. Not the documentation kind — the "here's what actually happens and why it matters" kind.
A ransomware simulation post reached 50,000 views. Messages came from security professionals, students, engineers across continents. Technical depth doesn't scare people away. It draws in the right ones.
I spoke in Morocco about Zero Trust — not as a buzzword, but as a philosophy for building systems that assume the worst and still function. I've given over five online conferences on cloud infrastructure and systems engineering, sharing lessons from production with anyone willing to listen.
Read my articlesI do research by passion, not obligation. Understand deeply, build cleanly, share clearly.
Cloud mastery. AI integration in cybersecurity. Infrastructure design as a discipline, not a checklist. Creating educational platforms that respect the learner's intelligence.
Building something meaningful in Morocco — not nationalism, but recognition that infrastructure shapes economies, and economies shape lives.
Infrastructure is never neutral. It reflects the intentions of the one who designs it.
If you've read this far, we probably think alike.
Email : [email protected]
Get in touch