I turn business constraints, organizational complexity, and technical risk into resilient platforms and engineering systems that teams can govern and evolve.
Systems thinking is the practice behind the title. I make the forces around a system visible before choosing the structure inside it.
STEP_01
Define the boundary
Name what the system owns, what it depends on, and where responsibility changes.
STEP_02
Surface the forces
Make business goals, technical constraints, incentives, risks, and organizational topology visible.
STEP_03
Protect the invariants
Establish the contracts and properties that must remain true while implementations evolve.
STEP_04
Design for failure
Contain faults, expose degraded states, and make recovery an architectural concern.
STEP_05
Close the feedback loop
Connect architecture decisions to operational, delivery, quality, and user signals.
STEP_06
Preserve options
Sequence decisions so the system can adapt without uncontrolled rewrites or permanent lock-in.
[ SYSTEMS_PRACTICE ]
Systems I Work Across
The systems contexts where I do my best work - shaping boundaries, operating models, and technical direction across the whole.
Platform systems
Shape shared capabilities, ownership boundaries, and paved roads so the safe path is also the easier path.
Distributed systems
Design contracts, failure containment, degraded operation, and recovery across service and product boundaries.
Teams and technology
Treat team boundaries, incentives, review capacity, governance, and decision flow as part of the system.
AI delivery systems
Build validation, privacy, quality, and review controls around AI-assisted engineering workflows.
Technical strategy
Sequence decisions, make trade-offs explicit, and preserve options while systems and organizations change.
[ PEER_EVIDENCE ]
Peer Perspectives
Corroboration from collaborators and leaders who have seen the work from inside the system.
“Mohamad is one of the best engineers I have worked with in my career. His technical skills are excellent and his attention to detail and willingness to jump in to solving any and every problem is admirable. I was most impressed with his ability to understand and solve complex problems very quickly.”
Mikko Hyppönen
ENGINEER, LEADER, MENTOR
“Mohamed somehow found time on weekends and evenings to meet the demanding requirements that come with growth. He was always cheerful and led reorganizations which was key for others as they like to naturally question change. A natural cultural leader.”
Peter Jackson
BOARD MEMBER, CHIEF STRATEGY OFFICER
“Mo always understood infrastructure complexities and limitations, adjusting application architecture and aligning its design to fit current system capabilities. Whether it's databases, networking, security, AI/LLMs, Mo will always figure it out.”
Alexey Popovich
PRINCIPAL INFRASTRUCTURE ARCHITECT
“He's the epitome of what anyone would want in a technical lead - he could handle any of the tasks on the list, but he also knows who the right person is for the job. He has a clear head for design, smoothly fitting all the pieces together across the whole stack.”
Jeremy Nicholl
SOFTWARE DEVELOPER
[ ARCHITECTURE_JOURNAL ]
Architecture Notes
Public working models for AI engineering, governance, platform thinking, and the systems around software delivery.
Quality & Governance
The Review Bottleneck: Software Engineering After Code Becomes Cheap
AI moved the software delivery bottleneck from implementation to review. Teams need risk-tiered review contracts, not larger queues of unread generated code.
The Liability of Code: Software Engineering After AI
In AI-assisted engineering, code is a liability carrying token cost, long-term support cost, and governance risk. The strongest engineer minimizes code while governing durable systems.
Escaping Generative Monoculture in AI-Assisted Engineering
AI coding assistants accelerate routine implementation, but their statistical defaults can narrow architecture choices. A practical framework for preserving engineering divergence.
Join the mailing list to receive notifications for future articles, engineering logs, and architectural deep dives. No spam, just technical deep dives.
