Eight years spent inside software other people wrote, making it measurably faster.
Architect at Systems Limited, on RakBank. 40 to 65 percent faster, measured. Five years leading a team of developers while still writing code most weeks.
I'm Faran. Banking, commerce, digital asset management. I find where the time actually goes, rebuild that part first, and keep releases running while I do it. Eight platforms so far; the improvement usually lands between 40 and 65 percent.
For five of those years I also led the team doing it: hiring, onboarding, reviews, the difficult conversations, while still writing code most weeks. I've never been convinced you have to choose one.
Not where people assume it goes. Measure the load path, the queries, the processing ceiling, then write down the number we intend to beat.
Incrementally, behind the running product. You don't get to pause a bank, a storefront, or a team's roadmap for a rewrite.
Boundaries the next engineer can find, and a team that knows why the decisions were made. That part is the leadership half of the job.
A six-year-old banking platform with more than half a million customers on it, where every change had become slow and expensive to make.
Architected the redesign and the migration to React and TypeScript, shipped incrementally alongside the live platform rather than as a cutover.
A Salesforce Commerce Cloud storefront that was costing conversions every day it stayed slow. The kind of problem everyone sees, and nobody owns.
Designed and delivered a PWA to replace the storefront, leaving the commerce backend and its integrations where they were.
Five years on a digital asset management platform built on microservices, and a team to build it with. Processing became the ceiling as customers grew.
Owned the Vue and TypeScript SPA and the service architecture end to end, designed a Kafka event system to lift the ceiling, and ran the team through it.
Vehicle tracking drowning in its own telemetry. Every device talking constantly, and a backend paying for all of it.
Rebuilt the ingest path and tuned MQTT so the fleet reported what mattered at the rate it mattered.
Reviews scattered across Google, Facebook and Yelp with no single view, on a schema that buckled as volume grew.
Aggregated all three sources, built the CI/CD pipeline, and redesigned the schema for volume. My first time leading a team.
Automotive maintenance and VIN-based parts ordering, where the people doing the work had no usable view of the fleet.
Built the dashboards fleets actually ran their day on, over the VIN and parts data.
A print business trapped in legacy PHP, where every new feature cost more than the last.
Migrated it to Angular and Node and added real-time collaborative editing. The first legacy migration I ran. It became the specialty.
Property booking that could not surface the right property. The catalogue was there, the retrieval was not.
Put Elasticsearch behind recommendations and tuned the read path until search kept up with the traffic.
Lint, type-check, and test standards for TypeScript projects: a scaffolder, shared ESLint config, and custom rules.
Local-first viewer for AI coding-session history across Claude Code, Codex, Copilot, Cursor, OpenCode and more. Astro + Deno Desktop, six languages including RTL.
A local-only Chrome DevTools panel that watches the inspected page and reports cross-browser compatibility risks in its HTML and CSS.
A native-messaging bridge for driving Firefox from Claude
Open to full-time architecture and lead roles, and to shorter engagements where a platform needs unblocking.