Software engineer · founder · product builder · technical architect

SEIF
MOUSTAFA

I take software from the messy idea to the working product.

I work across product, architecture, .NET, Next.js and Flutter—so I can stay with the problem instead of handing it off at every layer.

Founder / SCRIPEProduct + technical ownership
BTD / tooling
$ btd doctor
✓ architecture healthy
AstraFlow / open sourceawait mediator.Send(command);
Cairo / Egypt
Founder of SCRIPE.NET backendsNext.js productsFlutter appsOpen source
Selected work / five systems I know deeply

Different products.
Different engineering problems.

Scroll slowly. Each stop shows what the product is, what I owned, and why the engineering mattered.

01 / 05
Scroll ↓
01 / 05 · Founder-led product ecosystem

SCRIPE

I’m building SCRIPE as one operating system for the work around a sports academy—not another isolated booking or admin tool.

Founder · Product/Technical Architect · Primary Developer.NET 10 · Next.js 16 · Flutter · Modular Monolith
Open case study ↗
SCRIPE / ACADEMYOPERATIONS
AcademyAcademy statusSessionsTodayTeamsActive
U16 / Training18:00U14 / Recovery19:30
More work

Depth first.
Breadth still matters.

The flagship work tells the strongest product story. These case studies and earlier projects add package design, platform thinking, and professional delivery work.

Open source

I also build tools
for other developers.

Public packages force a different discipline: the API, errors, docs and defaults all have to make sense to someone who cannot ask me what I meant.

Open-source work ↗
How I work

How I usually attack a software problem.

01

Start with the product.

If I can’t explain the user, the workflow and why it matters, choosing a stack is premature.

02

Keep boundaries explicit.

Domains, permissions, data ownership and API contracts should be understandable without archaeology.

03

Build the surface too.

I don’t stop at the backend. Web and mobile are where the architecture finally meets a person.

04

Ship the boring parts.

Errors, auth, configuration, deployment and the last 10% are what turn a demo into software.