Slow-speed riding, track-stand games, and the kind of unhurried saddle time that makes the rest of the ride feel obvious.
A small group meets in the park. We work the boring fundamentals — pedalling circles, looking up, weight on the bars vs. the saddle — until they aren't boring anymore. 90 minutes, taught. Bring any bike. First one's free if you're new.
Same place, same morning, no instruction. We just ride together at low speeds and play. You're on your own bike under your own insurance — I'm there as a fellow rider, not a teacher. Show up if it's your kind of thing.
An hour where someone is paying full attention to what you have to say. No advice unless you ask. No agenda but yours.
You talk. I listen. You decide whether you want me to reflect back, push gently, or just hold the silence. We meet in person where possible, on a call where it isn't. There is no script, no framework, no "session structure" beyond your hour and my attention.
Some people come monthly. Some come once. Both are fine.
A long, low room. Brass and crystal bowls. You lie down. The room fills with sound until thinking gives up.
A 75-minute group bowl sound bath. You're horizontal on a mat with a blanket. I play a small set of singing bowls and gongs. Most people drift somewhere between sleep and wakefulness. Many leave quieter than they came.
No experience needed. Wear something you can lie down in for an hour without thinking about your zip.
A specific question, asked carefully, answered with a pendulum and a map. Findings posted back to you within a week.
You send a question, an address or a coordinate, and whatever context helps. I work the question with rod and pendulum over a printed map, write up what came back, and post it to you within seven days. Most questions are about land, water, or whether to do the thing.
This works whether you're in Cornwall or California. Asynchronous on purpose.
Sometimes you need a careful pair of eyes on a codebase that has grown organically. Sometimes you need a small product shipped on the edge in days. Sometimes you need internal tooling that doesn't make people sigh. I work in all three modes — pick the one that fits.
I come in with fresh eyes and a soft scalpel. Find what's dead, what's duplicated, where boundaries blurred. Then a tier'd plan — sweep, then de-duplicate, then re-shape — without a rewrite.
Small, fast products on Cloudflare's edge — Pages + Functions + D1 + R2 + Zero Trust Access — from a one-page spec to a deployed URL with tests, in days not months. Spec first, then a tiered plan, then I build.
Devcontainers, CLIs, TUIs, scaffolds — the unglamorous infrastructure that makes a team's daily work smoother. Treated with the same care as product code: typed, tested, documented, no surprise dependencies.