One moment / Route transition
The page is being assembled. Navigation remains available while the content catches up.
Software engineer · Product maker
I'm Ali, a full-stack engineer with six years inside dental laboratories. I design and build web and desktop systems where clarity, precision, and operational reliability matter.
Available for selected product engineering and frontend work · Remote from UTC+3
1 product
Built, deployed, and sold
Oscar Lab System
6+ years
Inside dental laboratories
Operational domain experience
93.8%
Computer Science result
Bachelor's degree
Web + desktop
Products across environments
Next.js · .NET · WPF
Product personality on the surface. Engineering evidence underneath.
01 / Flagship product
Product status
Shipped and sold · 2024
Built from inside the problem. Oscar replaced fragmented laboratory records with a dependable desktop workflow for cases, billing, payroll, and reporting.
Open full case dossierA cloud product direction for connecting laboratory operations, clinical records, scheduling, and collaboration.
A desktop research system exploring five-dimensional hyperchaotic encryption for highly correlated digital images.
The visual personality changes with the product. The way I discover, model, test, and evaluate the work stays consistent.
People · constraints · exceptions
Ownership · recovery · data
Clarity · speed · accessibility
Evidence before claims
Origin / The first workshop
Before software, I spent six years inside dental laboratories, where materials, handoffs, and small errors had physical consequences.
That background changed what I notice: where a workflow loses information, where ownership becomes ambiguous, and where a polished surface hides a weak foundation.
Working with real materials taught me to respect constraints, tolerances, and irreversible decisions.
Daily laboratory work exposed the gaps between people, paper records, financial tracking, and production status.
Oscar became the bridge: domain knowledge translated into workflow, interface, architecture, and delivery.
The medium changed. The habit of observing, testing, and refining did not.
Read the full origin storyChapter 03 / Engineering notes
Selected field notes on visual systems, failure-safe architecture, and performance—the reasoning that rarely fits inside a project screenshot.
Open the writing archive
Featured noteHow visual language, density, and component rules can make a specialized product feel like a tool instead of a template.
A walkthrough of ownership, transactions, and recovery paths in a checkout flow designed around failure—not just the happy path.
Read the noteNotes on balancing expressive 3D product work with loading strategy, device constraints, and useful fallbacks.
Read the noteChapter 04 / Start here
I’m most useful when a product has real operational complexity: tangled states, specialist users, difficult handoffs, or an interface that has to make all of that feel clear.