I’m a web development professional who turns operational needs into practical digital workflows.
I map processes, coordinate teams, and build dependable applications with modern tools—from requirements through delivery.
CURRICULUM VITAE
Download my CV for a closer look at my experience, skills, and professional journey.
Download CV ↓WORK
Preparing an Odoo Budget Usage import used to run three to four months. Multi-sheet Excel now converts in a single pass, with every cost center and COA validated against Odoo before the ZIP is written.
650 assets — NUCs, PCs, laptops, printers, CCTV — had no asset management at all. They now sit in one platform alongside employee records, data center inventory, and master data.
A Node.js agent that reads each machine’s real hardware — RAM, CPU, free disk — every three minutes, and heartbeats whether someone is actually using it. The monthly audit went from a week of walking desk to desk to 10–15 minutes, measured from the hardware instead of a clipboard.
Attendance recaps for payroll took 60 to 180 minutes per period. The Excel now builds itself from Odoo overtime and leave data — what is left is a copy-paste.
Operational reporting meant pulling Odoo data by hand, remapping it, then rebuilding every chart. Odoo now feeds the dashboard and Power BI directly, so a change upstream shows up on its own — next to live CCTV over HLS and LHP inspection reports.
Odoo Monitoring Observer snapshots Odoo every six hours, so accounting can diff a COA between any two dates. Working out which account actually moved used to take hours of manual comparison.
Every Odoo change used to be written up by hand. A Discord bot now captures updates as they are discussed and files them itself, so the release history stays current without anyone maintaining it.
Odoo will not tell you which approver is holding up an AR helpdesk ticket, so I built the view it was missing. Tracing one used to cost 15 to 45 minutes; now helpdesk reads it off a list.
Spending notes scattered across apps and paper, pulled into one place and categorised. Set a budget and a period, and it works out the daily limit that tells you when to stop.
Checking server health meant SSHing in and reading terminals one box at a time. Metrics, logs, uptime, and container telemetry now land in a single Grafana view.
Preparing an Odoo Budget Usage import used to run three to four months. Multi-sheet Excel now converts in a single pass, with every cost center and COA validated against Odoo before the ZIP is written.
650 assets — NUCs, PCs, laptops, printers, CCTV — had no asset management at all. They now sit in one platform alongside employee records, data center inventory, and master data.
A Node.js agent that reads each machine’s real hardware — RAM, CPU, free disk — every three minutes, and heartbeats whether someone is actually using it. The monthly audit went from a week of walking desk to desk to 10–15 minutes, measured from the hardware instead of a clipboard.
Attendance recaps for payroll took 60 to 180 minutes per period. The Excel now builds itself from Odoo overtime and leave data — what is left is a copy-paste.
Operational reporting meant pulling Odoo data by hand, remapping it, then rebuilding every chart. Odoo now feeds the dashboard and Power BI directly, so a change upstream shows up on its own — next to live CCTV over HLS and LHP inspection reports.
Odoo Monitoring Observer snapshots Odoo every six hours, so accounting can diff a COA between any two dates. Working out which account actually moved used to take hours of manual comparison.
Every Odoo change used to be written up by hand. A Discord bot now captures updates as they are discussed and files them itself, so the release history stays current without anyone maintaining it.
Odoo will not tell you which approver is holding up an AR helpdesk ticket, so I built the view it was missing. Tracing one used to cost 15 to 45 minutes; now helpdesk reads it off a list.
Spending notes scattered across apps and paper, pulled into one place and categorised. Set a budget and a period, and it works out the daily limit that tells you when to stop.
Checking server health meant SSHing in and reading terminals one box at a time. Metrics, logs, uptime, and container telemetry now land in a single Grafana view.