A wall of technology logos would not tell you much. These projects show the starting situation, what I personally owned, and the engineering decisions involved. The full archive is broader and considerably less polished.
A live IBM Domino platform used by a directorate and a network of 100+ institutions. I did not treat it as a one-off redesign: the work covered terminology and data modeling, permissions, reporting, security, user training, servers, and day-to-day operations.
An ERP for property technical support where the digital workflow starts with physical equipment. A technician scans a QR code, opens the asset and task, talks to a manager, and completes the job while administrators manage sites, roles, and access.
A field system for inspectors and a client portal on one backend. The workflow included routes, forms, photos, measurement-device data, automated PDFs, and a separate migration of roughly 70,000 historical reports from Google Drive into Supabase.
The methodology evolved while the product was being built: the questionnaire grew, peer feedback was added, and interpretation rules became more sophisticated. I translated that moving logic into a product with stable scoring, normalization, admin tooling, and visual PDF reports.
A platform for generating ready-to-sell digital products with AI. The central engineering problem is not merely connecting a model, but making a non-deterministic process manageable: persisted generation state, iterative refinement, clear intent/execution/asset boundaries, and auditable SQL logic in git.
