I'm a physical therapist. I got into this field because I wanted to help people move better, get back to the things they love, and understand why their body does what it does. That part is still the best part of the job.
What no one tells you in PT school is that you'll spend a meaningful chunk of your career writing documentation that patients will never read, for insurance companies who treat it as a hurdle rather than clinical communication. I got tired of it.
So I started building. I had no coding background — just curiosity, a lot of free YouTube videos, and a very specific problem to solve. The first thing I made was a single HTML file that calls an AI API and generates clinical notes. It took my end-of-day documentation from 90 minutes to about 15.
Now I'm learning properly. Working through fundamentals, building things that matter to me, and writing about what I find. The intersection of clinical expertise and technical capability is almost completely unexplored — and I think that's where the most interesting work is.
Clinically, I specialize in orthopedics and post-surgical rehabilitation. I've worked in outpatient, acute care, and sports settings. I care a lot about outcome measurement, evidence-based practice, and making sure patients understand what we're doing and why.
On the technical side, I'm a beginner — but an unusually motivated one. I'm working through a self-directed curriculum covering HTML, CSS, JavaScript, APIs, and eventually React and serverless deployment. Everything I build comes from a clinical problem I've actually experienced.
I think there's a version of healthcare administration that doesn't crush clinicians. Building toward it, one tool at a time.
If you're a clinician curious about building tools, a developer interested in healthcare, or just someone who found something useful here — I'd like to hear from you.