what-i-do
What I actually build.
I'm an independent Brussels web developer with fifteen years behind me, from the company website to the complex platform: website development in Brussels with TypeScript, Next, Nuxt and Laravel, and WordPress development in Brussels where WordPress is genuinely the right tool. On a grant-eligible project my role is twofold: deliver the technical work, and give you the documents you'll be asked for. A precise offer, a bounded mission, a demonstrable deliverable.
full-stack
Full-stack development
Teams that need a senior engineer who can build the whole thing, not just one layer.
Web platforms built end to end (interface, application, and the APIs underneath) with TypeScript, Next, Nuxt, Laravel, or WordPress where they fit, and whatever else the job actually calls for.
Production software, documented and owned by you.
devops
DevOps & cloud
Teams whose deploys are slow, manual, or scary.
Docker, CI/CD, and cloud infrastructure on AWS or DigitalOcean: deployment pipelines and environments that ship themselves and stay up.
Releases that are routine instead of an event.
consulting
Technical leadership & consulting
Teams facing decisions that a permanent CTO hire would be too much for.
A senior pair of hands on the hard calls: architecture, technical direction, and the trade-offs that decide whether a build succeeds or stalls.
Decisions made and owned, with someone accountable for the trade-offs.
code-audit
Audit & due diligence
Investors weighing a deal, or founders deciding whether to extend or rebuild.
An independent read on a codebase, architecture, or team, delivered as findings and recommendations you can act on, not a vague score.
A clear, defensible basis for an expensive decision.
training
Training & enablement
Teams that want to level up their engineering practice for good.
Hands-on sessions built around a team's own codebase: language, tooling, workflow, and the practices that make change cheaper.
A team that ships with more confidence and needs less rescuing.
ai-engineering
AI-assisted engineering
Teams adopting coding agents who need it to be an engineering practice, not a per-developer experiment.
One shared configuration for rules, tool access and reusable instructions, versioned with the code and applied whichever tool a developer drives; deterministic checks and reviewed diffs around every change; sandboxing the tooling cannot switch off; and working sessions on where this earns its place and where it doesn't.
One way of working the whole team follows, with the risky parts contained.