The Moment a Clinical Tool Becomes Infrastructure
A short introduction to a DoctorsWhoCode series on spreadsheets, tests, and retrieval as the basic discipline of physician-built clinical software.
· 7 min read
From Excel to Python: When Your Spreadsheet Becomes a Liability
Excel is often the right first move for a physician-builder. The problem begins when clinical logic stays trapped in a container that can no longer safely hold it.
· 8 min read
Why Your Clinical Calculator Needs Tests
A clinical calculator is not safer because it is written in code. It becomes safer when its expected behavior is explicit, checked, and protected from silent drift.
· 8 min read
RAG Is the Bridge Between Medical Knowledge and Medical Practice
Clinical AI earns workflow trust only when its answers are grounded in current, local, auditable knowledge. Retrieval is not a feature. It is infrastructure.
· 9 min read
TypeScript: Because a Misplaced Decimal Can Hurt a Patient
Clinical software cannot afford vague inputs. TypeScript gives physician-developers safer contracts, clearer data shapes, and fewer silent failures.
· 11 min read
JavaScript: The Language Your Patients Already Run
Every patient portal, tablet consent form, and browser-based clinical tool already runs JavaScript. This is where physician-developers start changing what medicine feels like on a screen.
· 10 min read
The Physician-Developer's Stack: Nine Tools. One Doctor. A Workflow That Actually Ships.
A practical 10-part Doctors Who Code series for physicians who want to build and ship clinical tools with the modern web stack, from JavaScript to deployment.
· 6 min read
The Era of the Clinical Scratchpad: Why Every Doctor Should Build "Disposable" Software
For the past two decades, medical software has been synonymous with monolithic platformsEpic, Cerner, and their ilkmassive systems designed to serve e...