Mission & engineering philosophy
I'm a final-year Software / AI Engineering student at EMSI Marrakech, currently looking for a 6-month PFE internship in AI & Data Science. This site exists to show how I actually think through a problem — not just what I've shipped, but the reasoning behind it: what the constraints were, what I considered and rejected, and what I'd do differently next time.
A CV or a list of repositories can show what was built. It can't easily show how a decision got made. That's the gap I want this site to close — a real, checkable record of engineering judgment, alongside the code itself.
How I work
Reasoning over adjectives
I'd rather show the trade-off I made and why than describe something as “innovative” or “robust” and ask you to take it on faith.
Depth over breadth
A handful of projects explained thoroughly — constraints, approach, trade-offs, results, what I'd change — says more than a long list of things I've touched.
Say what's real
If something is planned rather than built, I say so. I'd rather be accurate than impressive.
Ship the proportionate thing
I pick a tool or a technique because a real requirement calls for it — not because it's the technology getting attention that week.
What I work with
Languages
AI / Machine Learning
Backend & APIs
Frontend
Data
Tooling & Deployment
Right now
- Finishing my final year at EMSI Marrakech and applying for a 6-month PFE internship in AI & Data Science.
- Working as a Web Development Intern at Southydraulic, building a full-stack hydraulic project management tool.
- Rebuilding this site's structure and content in phases — the reasoning behind each phase is documented in this project's own repository.
These aren't abstract values — they're the same principles that govern how this site itself is built and documented; the reasoning behind every non-trivial decision on this project is written down in the project's own documentation.