Lugu Technology Limited

My background is in electrical engineering, which is probably why I care more about whether a system actually works under real conditions than how it looks in a pitch. That carried straight into how I build software: I'd rather ship something that runs in production than something that only holds up in a demo.

Over the years that's meant building a genuinely wide range of systems — e-commerce platforms handling real checkout and payments, internal management tools for gyms and construction billing, a ledger-based investment platform built double-entry from the ground up, booking and invoicing systems for service businesses, and desktop and mobile apps built with Electron and Flutter where a browser tab wasn't the right tool for the job.

Most of what I build runs on PHP and MySQL — deliberately. It's dependable, it deploys cleanly on ordinary hosting, and it doesn't require a client to maintain a complicated build pipeline just to keep their own website running. But I don't force every problem into one stack: when a project genuinely needs Laravel's structure, or a Node-based real-time service, or a native desktop app, that's what it gets. The tool follows the problem, not the other way around.

Security isn't an afterthought I bolt on at the end — proper password hashing, CSRF protection, and rate-limited authentication are part of how I write the first version of any login system, not a checklist for later. And every project I take on gets the same standard: deployed to real infrastructure, documented, and handed over in a state where you actually own it — not locked into me or a platform to keep it running.

If you're looking for a developer who'll build you something polished-looking that falls over under real use, I'm probably not the right fit. If you want something that actually works — and keeps working — that's what I build.