Contact
Email is best. I read everything and reply to what I can.
The reliable way to reach me is email. I’m not fast — a few days is normal, longer when work is loud — but I do get to it.
If you’re writing about something specific, the list below is roughly what I’m useful for.
What to write about
Product engineering work
Roles or projects that want someone who can sit with a product manager on Monday and be deep in the data model by Wednesday. I’m selectively open — building something together, or just comparing notes.
Architecture and system design
High-scale distributed systems, PostgreSQL and query optimisation, event-driven architecture with Kafka or RabbitMQ, and the reliability work that surrounds them. Happy to be a second pair of eyes on a design doc.
Coaching and mentoring engineers
Growth conversations, promotion cases, or engineers trying to work out what senior actually means in practice. This is the part of the job I’d least like to give up, so I’ll usually make the time.
Propklar
If you own or manage property and the numbers never quite add up, I’d like to hear how you’re handling it today. I take demo calls myself.
Speaking and writing
Talks, podcasts, or writing about any of the above.
Something else
If it doesn’t fit the list, write anyway. Tell me enough context that I can actually be useful, and I’ll read it properly.