Learn to Code
Build the habits and technical vocabulary required to turn a bounded problem into working software.
Physician-Developer Academy
Doctors Who Code is a guided learning platform for physicians who want to understand software, use AI with judgment, and build clinical tools that survive contact with real practice.
Learning Paths
The archive contains the full body of work. These paths give selected articles an instructional order and a project at the end.
Build the habits and technical vocabulary required to turn a bounded problem into working software.
Move from isolated prompts to observable clinical workflows with deliberate human checkpoints.
Translate clinical rules and workflow knowledge into tested, deployable tools.
Featured Start Here Guide
Do not begin by trying to understand the entire software landscape. Choose the path that matches your present work. Complete its first course in order. Build the project before adding another course.
Open Start HerePhysician-Built Projects
The platform teaches from working examples built inside clinical practice, not from abstract product exercises.
Clinical Decision Support
SMFM fetal growth restriction guidance translated into a bedside delivery-timing tool.
View projectOpen Medical Education
Open-source maternal-fetal medicine education, clinical references, and physician-built tools.
View projectClinical Workflow Systems
Physician-led documentation, coding, and workflow architecture built from clinical practice.
View projectLatest from the Journal
GitHub Gists look like scratch space for code snippets. Used correctly, they become a version-controlled clinical reference library that decks, apps, and blog posts can all cite from a single source.
Clinical AI can fail without crashing. Physician-developers must build the monitoring, outcome linkage, and human checkpoints that keep cleared software safe after deployment.
Clinical teams do not move slowly because clinicians are slow. They move slowly because pages, meetings, and verbal handoffs force physicians to keep re-explaining decisions that software should carry forward.
AI makes clinical software cheap to produce. It does not make it safe. Physician-developers must build systems in which speed remains subordinate to evidence, judgment, and the doctor-patient relationship.