About | Codeshark

I started Codeshark at 17.

Not with a business plan or a network or any real idea what I was doing. A project needed building, I built it, and that turned into another one. The nickname "Codeshark" came from early clients. Meant as a compliment, I think, and it stuck. Eighteen years later — more than half my life — here we are.

Most of that time wasn't spent as a hired developer. I've been a co-founder. That means I've sat in the room where the hard product decisions get made, not just implemented them. I've had real stakes in the outcome, felt the pressure of users not showing up, and made the calls about what to build next when the runway was short. Across nine startups, up to C-level. You get a particular kind of education doing that, and it's one you can't get any other way.

What does that mean? I've been inside enough early-stage products to recognise the patterns before they become problems. The teams that over-build. The architecture that looks fine until year two. The technical argument that's actually a product question in disguise. That kind of knowledge only comes from having lived through it, and it's harder to find than raw technical skill.

The work itself is full-stack, front to back, product thinking to implementation. I work with startups and small teams that need a technical partner who can operate at both levels: strategic decisions in the morning, code in the afternoon. Mostly remote, global, and selective about what I take on. I'm not here to fill a resource gap. I'm here to help you ship something worth shipping.

If any of this resonates, get in touch. I'd like to hear what you're building.

Get a second opinion on what you're building.

A short call with me directly. Tell me what you're building and where it's stuck, and you'll leave with a clearer next step. If I'm not the right person for it, I'll point you to someone who is.