About me

I started on the frontend and stayed there for a long time — the interface is the only part a user ever sees. But in systems like CRM and LMS the frontend runs out of room quickly: if the database is modelled wrong, no amount of React optimisation will save it. So I learned Node.js and Express, then NestJS and PostgreSQL. Today "frontend" and "backend" aren't two jobs to me — they're two sides of one product.

The way I work is simple: understand the problem first, write code second. On day one of a project the question I ask isn't "which framework" but "who uses this, how often, and on what device" — the answer decides both the architecture and the design.

Speed isn't an aesthetic to me, it's a requirement. On the Agency's LMS I brought Largest Contentful Paint down from 4.1s to 1.7s; at Energy Trucking I cut application load times by 20–30%. Behind those numbers is a plain fact: a slow site is an abandoned site.

Quality works the same way. At the bank I introduced a Jest unit-testing standard across the frontend codebase and pushed coverage on critical modules past 70%. Tests don't slow the work down — they prevent the phone call on release night.

I also like explaining things. At Robotics Lab I mentored 10+ junior developers, and before that I taught maths to graduating students for free during the pandemic. Being able to make a complex thing simple is a developer's most underrated skill.