Azaeron
A workspace for invoices, quotations, payments, inventory and customer records, with business rules enforced behind the interface.
- Role
- Full-stack engineering
LOADING
Opening the page…
LOADING
Opening the page…
Software Engineer
I build software that has to work beyond the screen.
I work across product interfaces, backend services, APIs, data and delivery. I care about the details that make software dependable: clear states, sensible boundaries, useful feedback and checks before release.
What I care about
A record should be correct, a failure should make sense, and a change should be checked. Here’s how those concerns show up in the work.
Azaeron’s API checks the allowed transition and payment summary before changing an invoice, then records what changed.
Verity keeps the document version and source beside a finding. If analysis is unavailable, the review screen says so.
AccessForge checks a change with a new scan before calling it verified. A suggested fix still needs to prove it works.
01 / Public work
Four public experiences you can visit today. Zam Zam Academy is a hosted prototype; the other projects are live products.
A workspace for invoices, quotations, payments, inventory and customer records, with business rules enforced behind the interface.
A public platform that brings six centres, their programmes and shared resources into one coherent publishing system.
A product and project website for an aluminium fabrication business, designed to help visitors understand the work and move naturally into an enquiry.
A multi-page education website study covering academics, admissions, faculty, student life, notices and contact journeys.
02 / Current work
Systems that are functional enough to inspect, but still have important release work ahead.
A document review workspace that keeps findings tied to a version, source and uncertainty.
A multi-branch retail system taking shape around identity, catalogue, SKU, pricing and store-level operations.
A procurement workflow for project scope, pricing, approvals, supplier requests and purchasing records.
An accessibility remediation system that separates finding, changing and verifying so a proposed fix does not become proof by assumption.
From my notebook
Application state · 4 min read
What invoice and publishing workflows reveal about guarding transitions on the server.
About me
Banking transactions and public digital-service requests taught me to pay attention to the person behind a record. That still shapes the questions I ask when I write software.
More about my background