Observable behavior wins.
Source, logs, response headers, state transitions, exports, and repeatable checks beat confident guesses.
A generalist with production scars.
I have spent 26+ years building for the web and 13+ years close to WordPress, search systems, analytics, and performance. The through-line is implementation: find the layer that owns the failure, change it, verify it, and leave the system easier to operate.
The work I gravitate toward
Systems that have accumulated operational weight: several data sources, an awkward handoff, a queue nobody trusts, a private admin surface, a deployment that only one person understands, or a failure visible in the browser but owned somewhere else.
I am comfortable moving between application code, HTTP behavior, data, infrastructure, search, and measurement when the actual problem crosses those layers. I am equally comfortable deciding that a smaller change is enough.
What I will not manufacture
Anonymous client theatre, invented traffic gains, fake scale, or a technology list pretending to be a case study. Sensitive work stays redacted. Experimental work is called a lab. A build in progress is not described as a production outcome.
Operating principles
How I keep complicated work sane.
Recovery is a feature.
Retries, idempotency, backups, explicit dead states, and reversible releases belong in the first design.
Static until proven dynamic.
Do not rent a database, session, or client runtime to render content that changed in Git.
Boundaries create trust.
Private evidence stays private. Model output remains reviewable. Specialist content has one canonical owner.