The translation problem
Competent engineers and competent clinicians, shipping the wrong product anyway. What gets lost in the handover between them, why a requirements document cannot carry it, and what changes when one person holds both.
Most conversations about health technology have a clinician on one side and an engineer on the other. I am useful on a stage because I am on both sides at once, and because I have shipped something real to the professionals I am describing.
I have also been teaching for a decade, which is the part that matters for a room. Tutorial master through pharmacy school in the subjects students most often fail, and still teaching now, guiding candidates through licensing examinations across the RxHustle communities. I am used to an audience that did not arrive already convinced.
That is the healthcare half. I also speak on AI, software engineering and what it actually takes to learn to build, to technical audiences with no particular interest in pharmacy. Conferences, universities, company events, student societies and podcasts all work.
These are arguments I already hold, not a fixed catalogue. Each one gets rewritten for the room it is going into, and if what you need is close to one of them but not quite it, that is usually the more interesting talk. Tell me the audience and the brief.
Competent engineers and competent clinicians, shipping the wrong product anyway. What gets lost in the handover between them, why a requirements document cannot carry it, and what changes when one person holds both.
Governance rather than features in clinical software: why an audit log is not a control, when approved data should lock, and how amendments differ from edits. Drawn from building an EMR and a LIMS.
An honest build story: one person, a live platform for pharmacists, the architectural decisions that survived contact with users, and the ones that did not.
A practical case for clinicians learning to ship software: what changes in the product, what it costs you, and how to start without abandoning practice. Built for pharmacy schools and student federations.
Where a model earns its place in a real product and where it is theatre. The worked example is adaptive study inside a clinical education product, but the argument does not depend on healthcare and the talk is written either way, for a clinical room or a technical one.
Technical SEO reframed as a product requirement rather than a marketing one: what it means to be findable at the exact moment a professional needs you, and the structural work that makes it so.
Flutter, Firebase, and choosing an architecture one person can keep running alone. Drawn from two consumer apps shipped to both stores and a live health platform.
For people who did not study computer science and have a full-time job: what to learn first, what to ignore, and how to stay in it past the point where most people quit. Drawn from doing it, and from mentoring others through it now.
What to do when the gatekeeper is slow: distributing a Flutter build directly, running a product out of WhatsApp and Telegram, and arriving on Google Play with the audience already waiting.
Not on the list? Ask anyway. The only subjects I turn down are the ones I have no standing to speak on, and that is a shorter list than this one.
This page lists what I have actually done rather than what would look good. The teaching record is the long one; the conference record is the one that is still growing.