Let's talk.
Best inbox for long-form, social for anything shorter than a paragraph. All channels reach the same person.
Which channel fits
Save us both time — pick the inbox that's already tuned for your topic.
You have a build in mind
Email is best - describe the shape of the work, your timeline, links to any relevant repos or hardware. Expect a reply with a few clarifying questions, then a scoping call.
email meYou want me to talk to humans
Send dates, venue/format, audience, and roughly what you'd like covered. I'm happy to do remote panels, in-person talks (BLR + Asia, mostly), or pod guesting.
request a talkYou found a bug or want to chat
For code-shaped things, open an issue on GitHub - it's where I look first. For thoughts on a post or a build of your own, Twitter or email both work.
open an issueA few common questions
Answers to things people ask before they email.
How quickly do you reply?
Within 1–2 working days on email. Faster on Twitter DMs if I'm awake. If it's been five days, I almost certainly missed it — give me a friendly nudge.
Are you taking on new freelance work?
Selectively. I take on 1–2 engagements at a time, typically 4–12 weeks. The work I enjoy most lives at the firmware ↔ app boundary — Bluetooth/BLE, sensors, low-power, dev tooling.
Will you do a free consultation?
Short 30-min calls for scoping are on the house. Anything beyond that is billable, but the first meeting is meant to figure out whether we should even be working together.
I emailed but didn't hear back — did you ghost me?
Probably not on purpose. Check your spam, then send a one-line nudge. If your question can be a tweet, a tweet is sometimes faster.