What I actually do
New builds, rescue work on inherited projects, integrations between the tools a business already uses, and ongoing maintenance. The common thread is that someone needs a website to work reliably and needs a specific person to be responsible for that.
How an engagement starts
You describe the problem. I look at the site, the code or the brief, and come back with what I think is wrong, what I would do about it, roughly how long it takes, and what it costs. If the honest answer is that you do not need me, that is what you will get.
How I work
Small, visible increments rather than a long silence followed by a reveal. You get access to the work in progress, a written scope agreed up front, and changes to that scope discussed before they are built rather than after they appear on an invoice.
What I care about in a build
That pages load quickly on an ordinary phone on an ordinary connection. That the site can be used with a keyboard and a screen reader. That search engines can read it. That there are no secrets in the client bundle and no dependencies with known critical vulnerabilities. These are not add-ons.
Tools I work with
The stack is chosen per project. These are the technologies I reach for most often.
