Almost Thirty years in. Still shipping.

I've been building websites & software since the dot-com boom; back when the web was still working out what it wanted to be, and every new technology showed up promising to change everything. I taught myself C++, then Java, then PHP, mostly because I couldn't leave it alone. I wanted to know how the thing actually worked underneath.

Since then I've watched a lot come and go. Languages, frameworks, the trend of the year; most of it didn't last. The fundamentals did, every time. That's the main thing three decades drills into you: don't get precious about tools.

Tools are temporary. The problem you're solving is the part worth caring about.

After spending years away from full-time web systems development, I returned in June 2026 with a different philosophy. Modern tooling had changed completely, but the fundamentals hadn't, my stack today would be unrecognisable to the person who started out. TypeScript, cloud infrastructure, automation, browser tech, modern tooling in the loop while I work. It's made me faster, not smarter. What experience actually buys you isn't typing speed; it's knowing which problem is worth solving and what's going to break in six months. The tooling just clears the busywork so I can spend my time on the parts that matter: architecture and product.

I've got a low tolerance for complexity & friction. Most systems don't need half of what ends up bolted onto them. So I start every build with a deliberately boring question; "What's the smallest thing that still holds up once real people start using it?"

That question is the reason PageCraft is built the way it is. It was never meant to be "another landing page builder". I architected it as a modular platform where every major feature stands on its own, so I can add or change one piece without pulling the rest apart. That's the difference between a product I'm still comfortably improving two years in, and one I'd be afraid to touch.

The same instinct runs through the client work. Migrating a company off a broken Google Workspace setup, building an internal HR portal, turning a rough idea into a working MVP. I'm usually hunting for leverage, not reaching for another framework. More often than not, the right move isn't adding a technology. It's removing one.

Most of that work is rooted here in Melaka. I build for Malaysian businesses; the micro-sellers, home-based operators and small firms who need software shaped around how they actually run, not a shrunk-down version of something built for Silicon Valley. PageCraft speaks their language, literally: Bahasa Malaysia first, with DuitNow and WhatsApp where their customers already are. It's a market I understand from the inside because my wife and I run a dessert business from home as well.

On paper the things I've built have little in common: browser games, AI-powered products, internal business tools, a commercial SaaS. Underneath, they're the same job. Clean systems one person can maintain and keep evolving without the whole thing coming apart.

And that's the heart of it. Working solo, I don't hand things off between an architect, a designer, a QA team and a project manager. I'm all of them. Which means every shortcut I take today lands back on my own desk later. I'm the one still maintaining this after launch, so I've got every reason to keep it small, clean, and easy to reason about months down the line. Less code that works will always beat more code that impresses.

So Respawned isn't an agency, and it isn't freelancing in the usual sense. It's a studio of one. I design the system, write it, ship it, watch it run in production, and stay long after launch; because getting software out the door is the easy part. Keeping it standing once people depend on it is the real job.