About
I have been building software since 2013
I'm Mina Adel Naguib, a software engineer. I started with PHP and a school management system that people used every day. Thirteen years later I lead a development team, own the architecture decisions, and take the production problems nobody else can unblock.
Five years ago I joined an Odoo practice as it was being founded. There was no team, no shared codebase and no standards — I helped build all three. Most of what the team does today is a habit that had to be invented at some point, usually because something broke first.
In between, I spent a year leading instructors at an applied-technology school. It is the single reason my code reviews are any good: I stopped writing this is wrong and started writing here is what happens when this table has eighty thousand rows in it.
What I insist on
- Measure before you theorize. Most "the system is slow" problems are a specific, findable thing — and it is rarely the thing everyone assumes.
- A performance fix must not change what anyone can see. Same records, same permissions, before and after. Otherwise it is not an optimization.
- Never rename anything without moving the data with it. Renaming without a migration is silent data loss that surfaces weeks later.
- If I say something three times in review, it belongs in the standards. A rule I have to repeat is a rule that should be written down — or automated.
The route here
Thirteen years, one step at a time
I did not start with ERP. Every stop before it is why the ERP work holds up.
- 2013 — 2018
First production system
A school management platform in daily use. It taught me that the data model outlives every screen you build on top of it.
- 2018 — 2021
Full-stack & mobile
Websites, custom dashboards, mobile apps — and the phone systems and networks behind them.
- 2021 — 2022
E-commerce & payments
Online platforms and payment gateways. Handling money taught me to build things that reconcile.
- 2021 →
Odoo, from day one
Joined an Odoo practice at its founding — no team, no codebase, no standards. I helped build all three.
- 2023 — 2024
Teaching engineers
A year leading instructors at an applied-technology school. It is the reason my code reviews are any good.
- 2024 →
Technical team lead
Leading and mentoring a development team, owning the architecture and standards, and taking on the problems nobody else can solve.
No cost, no pitch
Book a free 30-minute call
Bring the problem you keep postponing. We will work out whether it is worth fixing, what it would take, and whether I am the right person for it.
- A slow system, and nobody can say why
- An upgrade that has stalled
- A build about to start, and you want a second opinion