Development
Software development, by stack
Most work arrives attached to something that already exists, so the first question is usually what it is built in. These are the stacks I work in most often, what I take on in each, and where the price comes from. If yours is not on the list, ask — this is what comes up most, not the limit of it.
I work on new builds and on code somebody else wrote, which in practice is most of it. Over a decade of professional work across PHP, Laravel, WordPress, TypeScript, React, Next.js, Vue, Node, Python and Go, plus the Postgres, Redis, Docker and CI underneath. One developer, so you talk to the person doing the work.
WordPress
WordPress runs a large share of Danish business websites, and a good many of them sit on a theme nobody has opened in two years. I build new WordPress sites, take over existing ones, write the plugin when a setting will not do, and keep the whole thing patched and fast.
Laravel
A lot of Danish business systems run on Laravel: customer portals, booking, invoicing, and internal tools that outgrew a spreadsheet. I build them, extend them, and take them over when the person who wrote them has moved on.
WooCommerce
A WooCommerce shop that is slow, or that needs somebody to retype every order into the accounting system, is losing money in a way you can measure. I build shops, fix the ones that are leaking, and connect them to the systems that should already know about the orders.
React
When the thing you need is closer to an application than a website — a dashboard, a customer portal, an internal tool people use all day — React is usually what it gets built in. I build those, and I join codebases that already exist.
Vue
Vue had a long run as the pragmatic choice in Danish web teams, which means there are a lot of Vue applications quietly running businesses whose original developer has moved on. Taking those over, getting them upgradable again, and continuing to build on them is work I do regularly.
Next.js
Next.js is what you reach for when a site has to be two things at once: fast and findable in Google, and an actual application behind the login. I build them, and I fix the ones where the second requirement quietly cost the first.
Not sure which one to pick?
Send a couple of lines about what you are trying to achieve. You get a reply within 24 hours, and an honest yes or no.