My experience is made of five bases.
Web, mobile, desktop, services and database. Since 1999, all five, in whatever language the job needed. Every rung of the helix is one of those five.
Muhammad Omais
I specify it. Then I design it, build it, or lead the engineers and designers who do, whatever the project needs. AI works alongside us every day, and the tools are the easy part. What you see here is what I do: take a rough problem, give it a shape, and keep going until it ships.
What I'm made of
Two strands, bonded: engineering and design. Experience across web, mobile, desktop, services and data made me an architect. Overseeing multiple projects made me a tech lead.
Web, mobile, desktop, services and database. Since 1999, all five, in whatever language the job needed. Every rung of the helix is one of those five.
I studied computer science and graphic arts. Code and design in the same person is rare, and it is why the system I specify is also the one people want to use. Each engineering base is bonded to a design base: W to UI, M to UX, D to VI, S to SD, B to IA.
When I analyse a problem I see the structure: what data comes from where, where each piece goes, and whether A has to be understood before it can be handed to B. When you have built every part yourself, you know what will break first and what will still be standing next year.
Because I can see the entire system, I can choose the stack, settle the architecture early and spot the technical hurdles before the team reaches them. Engineers move faster on a design they can see, and I stay in the code with them.
An enzyme is not part of the DNA, but it moves along it and makes everything happen faster. That is AI for me: it helps me build, manage and generate new ideas, every day. Someone still has to know when it is wrong.
The age of AI
What makes or breaks a project is the person guiding them: the experience to know what good looks like, the understanding of what the business needs, the judgement to pick the right tool for the job, the discipline to debug what comes back, and the ability to guide the AI, the team and the stakeholders through it.
Twenty-seven years of shipping is worth more than a faster model. I know what good looks like before the first line is written.
I know what your business actually needs it to do, who will use it, and what happens when it is wrong.
Sometimes it is a model, sometimes a query, sometimes a spreadsheet and a phone call. Choosing right is the first decision, and the cheapest one to get wrong.
A confident wrong answer looks exactly like a right one. I reproduce, isolate, test, and check the numbers against the source.
What to let the agent run, what the team must check, and what to promise the people paying for it. That is what makes or breaks a project.
The same request, the same model, started at the same moment. One side follows the instruction. The other asks a few questions first. An illustration, not a benchmark.
Tech lead
I'm the tech lead on the insurance mobile application for TruStage at Cognizant. I own the technical direction: the stack, the architecture and the standards. My job is to see the hurdles before the team hits them, and remove them when they do.
I pick what fits the problem, not what is fashionable, and write down why, so the team builds on decisions it understands.
Integration, performance, a dependency that will not behave: I look ahead for what will stop the team, and clear it first.
The team gets better, not just the code. AI tools included: I show people how to use them well and where not to trust them.
How a project moves
a hurdle comes to meI remove it and show the engineer how to handle it next time
AI, every day
I use AI to write code, analyse data, run agents, research and generate ideas. Pick a session to watch an example. These are illustrations of how I work, not claims about a client.
Answers come from your own records, not from guesses.
Ordinary code and people verify the work before anything irreversible happens.
You know what it costs to run before you commit to it.
Bring me a problem
A scripted preview of how I think, not a chatbot. A demo agent will show you how it works, then it is your turn.
company projects
side projects
I cannot show these screens, but this is what I have built for them.
Most of my work is done for companies. These are side projects I am free to share.
There is more. Much of my company work stays private. I am happy to talk it through.
Ask me about itAbout this site
I wrote the brief, designed the look and made every call. Claude Code wrote the code. One file, no framework, built over two days.
tried and dropped
10 Oct 2026
design ›a hero that builds itself, and a diagram of what I bring to a team
build ›one hand-written HTML file, with a terminal showreel of AI sessions
design ›bring me a problem: pick one and watch it get solved
build ›a scripted stage that answers six kinds of problem
design ›dark aurora, glass panels, headings that stream in like tokens
build ›a particle field that forms a problem, a system, a product and a check, and a demo agent that tries the tool first
design ›five pillars: knowing the tools is not enough
build ›two sessions racing side by side: same tool, different hands
design ›experience as a double helix: an engineering strand bonded to a design strand
build ›five genes that drive the helix, and bases you can light up
design ›solid ribbons with lettered base pairs, and a fifth base: services
build ›the hero and the helix split into sections of their own
build ›Three.js: a particle cloud with depth, an instanced-mesh helix, cards that tilt under the pointer
11 Oct 2026
design ›the five genes as tabs on one screen, and four facts on the first screen
build ›one helix instead of two, and a fix for reduced motion
design ›rewritten around the tech lead role: the stack, the architecture, the hurdles
build ›a lead diagram where each hurdle clears before the work goes live
Contact
Tell me what's not working. I'll reply with an honest view of how I'd approach it.
Email Omais