Introduction

I build small systems I can explain end to end: Java data-structure exercises, numerical solvers, game-tree search, reproducible ML pipelines, and a terminal status line I use every day.

Eight projects, November 2025 to October 2026, across five domains.

Time runs left to right; domain is the vertical lane. Lines are technical links, not chronology.

Tab to a project; ← → to move; Enter to open.

Selected projects

Systems diagram: eight projects plotted by date and domain

Eight projects. Select one to read its case study.

Time runs left to right; domains are horizontal lanes. Lines are conceptual links, not chronology.

General notes

About

Software engineering student studying AI & Data Science in Alexandria, Egypt.

Good work should hold up to inspection. A solver should match its reference, a model should survive an honest split, and a tool should disappear into the workflow it was built for.

My work sits where data structures, numerical methods, machine learning, game AI, and developer tooling meet. I have worked through array, matrix, and queue exercises in Java, implemented numerical methods from first principles, built a Connect Four engine around Minimax and Alpha-Beta pruning, compared ensemble models with nested cross-validation, and built a zero-dependency status line that runs in my terminal every day.

The projects on this sheet span November 2025 to October 2026. The methods change; the standard stays the same: understand the whole system, make the result reproducible, and leave fewer hidden assumptions than you found.

Project