About
A little context
With 5+ years building production systems, I design and build custom software that feels natural to use and easy to maintain. That might be a booking platform for a small tourism business or a data tool that finally gives a team the answers they need. I move between architecture and implementation comfortably, and keep the focus on outcomes that last.
I'm a full-stack developer and consultant based in Copenhagen. I've built systems for small local businesses and multinational companies. Their budgets and timelines differ wildly, but both need software that works reliably, can be maintained by someone else, and doesn't become a liability six months later.
I blend technical depth with practical delivery. I can architect a system and then build it. I can sit with your team to understand the messy reality of their workflow, then translate that into something that actually ships.
Most of my work comes from being comfortable in the uncomfortable middle: translating between technical and non-technical stakeholders, working in environments where mistakes are expensive, and moving between "we need this yesterday" and "this needs to last five years."
See examples of recent work →I default to collaboration over command. I'd rather understand someone's constraints than override them. The best solutions make everyone's job easier, not just the person who commissioned the work.
I bring energy to teams without demanding the spotlight. I push back on shortcuts that create tech debt, surface concerns early rather than let problems compound, and celebrate when something ships well.
My approach is democratic. I focus on clarity, momentum, and shared ownership. I adapt quickly to new stacks, new domains, and team dynamics. The constant is thoroughness: I like to understand problems deeply before proposing solutions.
I reach for Python and Django when I need something robust and maintainable. Node.js when the ecosystem fits. PostgreSQL when the data matters. React when interactivity is the point. The stack follows the problem, not the other way around.
I deploy with Docker and reach for HTMX when I need interactivity without the framework overhead. My Master's work in HCI/UX shows up in how I think about what users actually need versus what they say they want.
You get the person who designs it and builds it. No handoffs, no lost context, no playing telephone between strategy and execution.
I stay small on purpose. Every project gets my full attention, and you're never talking to an account manager who's never seen your code. If something breaks, you know exactly who to call.
And you get someone who genuinely enjoys the collaboration. I'd rather understand your constraints and build something that fits than propose an ideal solution that never ships.
I DJ and curate techno. Digging for tracks, building sets, and occasionally hosting events. Sound systems and audio workflows are a recurring side interest.
I enjoy mentoring junior developers and hosting small tech and creative meetups. Same instinct as the work: understand what someone needs, then help them get there.
If you're trying to figure out whether to build something custom or patch together another workaround, let's talk.