Work
Engineering Work
Detailed write-ups across delivery infrastructure, security, platform reliability, team standards and AI automation.
Delivery Velocity
Every change tested on a live store before it ships
An environment per pull request, a shared Playwright suite every store inherits, CI gates on performance and security, and deploys that roll back on a failed health check. Clients review real changes, and a bad release undoes itself.
Centralised Playwright E2E Framework
A shared Playwright test framework with per-store override layers — core checkout, account, and catalogue suites inherited by every client store on day one, with store-specific extensions layered on top.
CI Pipelines with Multi-Dimensional Quality Gates
CI pipelines gating on APM performance regression, Core Web Vitals delta, security scanning, static analysis, E2E tests, and peer review — nothing reaches production without passing every gate.
Ephemeral Feature Branch Environments
On-demand per-PR Magento environments provisioned automatically on pull request open, seeded with anonymised production data, and torn down on merge — giving every code review a live working environment to test against.
Zero Downtime Deployment Pipeline
Replaced manual SSH-based Magento deployments with a fully automated pipeline — pre-deploy validation, symlink-based atomic cutover, and automatic rollback on health check failure — achieving zero deployment-window downtime.
Security & Risk
Finding the holes and closing them fast
Vulnerabilities disclosed to Adobe and extension vendors, a patching framework that rolls fixes out across every managed store, and CI scans that stop malware and known-vulnerable packages before merge.
Automated CI Malware & Vulnerability Scanning
Malware detection, static security analysis, and dependency vulnerability scanning integrated as CI gates — running on every code change, blocking on detection, and alerting on new CVEs against installed package versions.
Emergency Patching Framework
Ansible-driven and Composer meta-package framework for rapid CVE response across a Magento portfolio — patches assessed, tested, and deployed across all managed stores within hours of a critical vulnerability being published.
Vulnerability Disclosures — Adobe, Amasty, Mirasvit, Pay360
Responsible disclosure of vulnerabilities across Adobe Commerce core and major third-party vendors, including RCE, stored XSS, SQL injection, and information disclosure — identified through platform-depth code review and security research.
Platform & Reliability
Infrastructure that stays up
The hosting platform, migrations off single-server and cPanel setups, verified backups and self-hosted tooling. Stores stay online through traffic spikes, server failures and moves, for merchants who can't justify enterprise hosting.
Centralised Backup with Cold Storage & Anonymised Dev Access
A centralised backup system spanning all managed Magento stores — automated snapshots, tiered cold storage, integrity verification on every backup, and a sanitised developer data pipeline that provides realistic local data without handling real customer PII.
High-Availability Magento Hosting Platform
Designed a flexible Magento hosting platform with support for high availability, autoscaling, and enterprise-grade performance at a fraction of the cost of enterprise hosting providers
Magento Infrastructure Migrations
Multiple full-stack migrations from legacy single-server and cPanel hosting to modern containerised multi-service architectures — zero-downtime DNS cutover, incremental data sync, and post-migration monitoring with warm standby rollback capability.
Self-Hosted Internal Tooling
Replaced SaaS subscriptions for error tracking, log aggregation, VPN, and CI runner capacity with self-hosted equivalents — maintaining full observability and security posture at a fraction of the equivalent SaaS cost.
Team & Standards
Standards the pipeline enforces
Local environments locked to production versions, and review rules backed by static analysis. New engineers get a working setup quickly, and quality holds whoever reviews the pull request.
Developer Environment Standardisation
Standardised local Magento development using Warden across the engineering team — locked service versions matching production, shared CLI aliases, an anonymised data sync tool, and an onboarding runbook that gets new engineers to a working environment in under an hour.
Engineering Standards & Code Review Culture
Defined architectural standards, module structure guidelines, and a structured code review process — enforced through static analysis, PHPCS, and peer review gates, not through documentation alone.
AI & Innovation
AI agents on real client tickets
Claude-backed agents wired into the bug workflow. They reproduce a client's report in a throwaway environment, draft the fix and put it through the same CI gates as code a person wrote.