The Rare Condition You Have Seen Ten Times
Why a physician's second brain turns scattered rare cases into a queryable clinical registry owned by the clinician who lived them.
· 7 min read
Clinical AI Should Help Us Find the Growth Restriction Cases We Miss
Fetal growth restriction is not just an ultrasound diagnosis. It is a longitudinal data problem. Clinical AI will not replace MFM judgment, but it can help surface the pregnancies whose risk is already visible in the record.
· 9 min read
The Lemonade Machine Problem
Automation in medicine should not be judged against an ideal clinician. It should be judged against real human variance, machine variance, supervision, and the cost of failure.
· 4 min read
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
You Are Still Prompting. You Should Be Building Agents.
Prompting has a ceiling. Once you hit it, you are coordinating every step manually while the AI handles individual tasks. Here is the framework and three live workflows I use to cross that line.
· 11 min read
Burnout Is Not From Working Too Hard. It Is From Working on the Wrong Things.
For physician-developers, burnout often comes from low-value technical friction. The answer is not more endurance. It is better delegation to systems, automation, and agents.
· 7 min read
I Gave an AI Agent 94 Skills and Let It Help Run My Clinical, Coding, and Theology Workflows
Three weeks into running Hermes Agent in production, I can say this: the real value is not the model. It is the workflow ecosystem wrapped around it. Here is what 94 specialized skills looks like in a real physician-developer stack.
· 12 min read
The Architecture Behind My 24/7 AI Operations Partner
The model is not the product. The workflow is the product. Here is a technical look at the production stack behind a physician-built AI operations partner: Docker, Traefik, model failover, rate limits, logs, HIPAA boundaries, and the failure modes I watch for every week.
· 13 min read
Dead Weight: What a 1970 Cardiology Textbook Taught Me About the Future of Clinical Evidence
A half-century-old textbook on congenital heart disease. A chapter on Ebstein's anomaly. A comparison that changed how I think about evidence, AI, and what we owe the next generation of physicians.
The Jetsons Problem in Clinical Medicine
Artificial intelligence in clinical medicine promises abundance. The real risk is not too little data, but too little agency, attention, and equity.
· 9 min read
Fluent Answers Are Not Clinical Judgment
Language models can make uncertain medical information sound finished. The problem is not fluency. The problem is mistaking fluency for accountable clinical reasoning.
· 8 min read
Journals Are Becoming Infrastructure
Medical journals are no longer only read by clinicians. They are becoming upstream inputs to AI systems. That makes provenance, evidence hierarchy, and distribution part of clinical infrastructure.
· 8 min read
The Search Box Is Disappearing
Medicine is moving from retrieval to synthesis. That changes the physician's work from finding information to judging synthesized information under clinical pressure.
· 7 min read
Fatigue, Failure, and the Data That Brought Me Back
After six weeks of missed training, my PGIS morning check-in revealed what a GPS watch alone never shows: glycemic and autonomic recovery run on entirely different clocks.
· 8 min read
My Slides Became Code: Why I Use Marp for AI-Generated Presentations
Marp lets physician-builders turn reviewed knowledge into version-controlled, AI-assisted teaching decks without surrendering clinical responsibility.
· 9 min read
AI Agents Do Not Replace Software Fundamentals. They Expose Whether You Have Any.
For physician-builders, agentic engineering is not prompt magic. It is bounded context, vertical slices, observability, and accountability.
· 8 min read
Codex on Mobile Solves the Async Doctor Problem
OpenAI bringing Codex into the ChatGPT mobile app is not about coding on a phone. It is about supervising agentic work when your clinical day refuses to give you uninterrupted time.
· 8 min read
The Map Has Blind Spots
Move 37 was not a parlor trick. It was a warning. Physician-developers need to be ready for the moment AI starts finding medically important patterns our inherited maps never taught us to see.
· 8 min read
AI Just Outperformed Physicians at Clinical Writing. This Should Not Surprise You.
HealthBench Professional shows AI has already crossed the threshold in clinical writing and documentation. The real lesson is not replacement. It is that physician-developers need to build the harness.
· 8 min read
When AI Told a Dying Man What He Wanted to Hear
Joe Riley trusted AI over his oncologist and died of a treatable cancer. His tragedy wasn't naivety — it was earned distrust, amplified by a machine that had no way to know the difference.
Deployment: When Your Code Becomes Clinical Reality
An app on your laptop helps no one. Deployment is the step where physician-developer work finally becomes available to patients, colleagues, and clinics.
· 14 min read
Postgres and Prisma: Where the Data Actually Lives
Clinical software becomes real when it remembers. This is the database layer that turns a one-off calculator into a longitudinal tool.
· 13 min read
Tailwind CSS: Design Without Asking a Designer
Patients do not trust ugly calculators. Tailwind helps physician-developers build interfaces that feel clean, credible, and ready to use.
· 11 min read
Astro: Building Fast, Clinical-Grade Websites Without the Bloat
Physician-developer projects are usually content-first. Astro fits that shape by shipping less JavaScript, faster pages, and cleaner performance by default.
· 14 min read
MDX: Where Writing Meets Code
Most physician writing dies in static documents. MDX turns clinical education into living pages that can explain, calculate, and update in one file.
· 10 min read
AI-Assisted Coding: Your Second Pair of Hands
Claude Code, Cursor, and Copilot do not replace judgment. They compress the feedback loop for physician-developers who still read every line before they ship.
· 13 min read
Python: The Language of Clinical Data
JavaScript runs in the browser. Python runs behind the workflow, where lab values, CSV exports, data cleaning, and clinical models actually live.
· 12 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
Deep Work for Physicians: Protecting the Cognitive Core of Medicine
Deep work is not a productivity hack for doctors. It is a clinical safety issue, a training issue, and a systems design issue. Physicians need to protect deep thinking and automate the shallows.
· 9 min read
The Human Bottleneck: Why Medicine's Agentic Future Is Waiting on Us
AI agents are 50x faster than humans, but medicine only captures a fraction of that speed. The real bottleneck in agentic AI is not the technology — it is human capacity, clinical oversight, and workflows built for the wrong consumer. A physician-developer's perspective.
· 7 min read
The Local Advantage: Why Physician-Developers Should Build on Local LLMs Instead of Consumer AI
Consumer AI tools like ChatGPT and Claude are useful. But a physician-developer who deploys a locally fine-tuned model on controlled infrastructure has something more powerful: a clinical tool that learns your practice, respects your data, and costs less at scale.
· 12 min read
Clinical Documentation Automation Should Remove Friction, Not Replace the Doctor
Documentation automation is not a typing solution. It is a workflow design problem. For physicians and physician-developers, the real goal is protecting clinical judgment from administrative drag.
· 8 min read
I Built PGIS Recipes Because Food Systems Need Architecture
PGIS Recipes started as a stack of Marp slide decks. I turned it into a GitHub Pages library because nutrition guidance only compounds when the delivery system is structured, durable, and easy to revisit.
· 6 min read
Why Doctors Should Learn to Code
Not to become programmers. To become the kind of physician who can close the gap between a clinical insight and a working solution.
· 4 min read
Doctors Who Code: Build Systems, Not Just Models
A TEDx pitch says physicians should build AI. I agree. But the work that matters is governance, validation, and delivery, not one-afternoon demos.
· 8 min read
Inbox to Insight: Building the DoctorsWhoCode Engine
Physicians do not have an information problem. We have a conversion problem. Inside the Telegram-driven research engine I built to turn links, papers, transcripts, and videos into drafts, PDFs, and durable editorial records.
· 10 min read
Doctors Who Code: From GitHub to Medical AI
A practical path for physicians who want to move from GitHub basics to building real medical AI projects.
· 4 min read
Your First Medical AI Project on GitHub: How to Choose One You Will Actually Finish
Most physician-developers never ship their first AI project. The problem is not skill. It is scope. Here is a framework for choosing a project that lands.
· 8 min read
Navigating Medical AI on GitHub: What Is Worth Your Time
There are thousands of medical AI repositories on GitHub. Most are abandoned, half-built, or unreproducible. Here is how to find the ones that actually work.
· 7 min read
JSON for Physicians: The Structured Data Your Clinical AI Actually Needs
A physician's guide to JSON, FHIR JSON, and structured clinical data for APIs, interoperability, and medical AI.
· 8 min read
Three GitHub Projects Physicians Can Actually Finish
Most physician-developer projects fail not because the ideas are bad but because the first build is too large. Here are three that are sized to finish.
· 7 min read
Your First Week on GitHub as a Physician: A Practical Starter Plan
Not a tutorial on becoming a developer. A seven-day plan for a busy physician to go from zero to a real project in a repository they will actually return to.
· 7 min read
GitHub for Physicians: Why Version Control Changes How You Build
Most physician-developers lose code the same way: no backups, no history, no way to recover. Here is why version control matters.
· 6 min read
Stop Lurking: Why Physicians Should Start GitHub Before They Feel Ready
Most physicians assume GitHub is for real developers. That assumption is costing medicine. Here is why the barrier is not skill, and what to do instead.
· 6 min read
The Referral System Is Broken for the Same Reason the Triage Line Is Broken
Nobody lost your fax. The system was designed to lose it. Referral failures are not clerical accidents. They are the predictable result of clinical infrastructure built for a different era.
· 12 min read
When Medical Algorithms Code Racism Into Patient Care
Race-based clinical algorithms in kidney care and obstetrics did not just reflect bias. They operationalized it. Physicians now have a responsibility to challenge the software, logic, and architecture that turn racial fiction into patient harm.
· 8 min read
I Built InboxDetox in Two Evenings — This Is What Disposable Software Looks Like
InboxDetox is an AI-powered email unsubscribe manager built in two evenings and deployed to Railway. It is on GitHub. Take it.
· 5 min read
Demystifying Digital Medicine Coding -- A Physician-Developer's Guide to Sustainable Telehealth Workflows
A practical breakdown of 2025 CPT telehealth codes, RPM billing thresholds, and the workflow engineering required to make digital medicine financially sustainable.
· 8 min read
Your Patients Are Already Using ChatGPT to Decide Whether to Call You
They are not asking it for fun. They are asking it because the triage line puts them on hold for 45 minutes. The threat is not the technology. The threat is the system that made the technology necessary.
· 10 min read
The EHR Vendor Wants You to Stay a Consultant
Physician passivity in health tech is not an accident. It is a business model. Understanding the structural incentives is the first step to building outside of them.
· 6 min read
Logs Before Intelligence: Why Data Discipline Must Precede AI Insight
Before you build any AI feature, you must first build the log. The principle every physician-developer needs to internalize before writing a single line of intelligence code.
· 8 min read
Your First Build Does Not Have to Save Lives
Every physician who codes started somewhere that had nothing to do with clinical AI. The first build is about identity formation, not impact. Here is why that distinction matters, and where to actually start.
· 6 min read
The Limits of Viability: What Patients Find Before They Find You
When families face periviability, they search before they call. What they find shapes everything. Here is why physician-developers have a responsibility to build better.
· 7 min read
When the Algorithm Fails, Who Answers for It?
Every physician using an AI tool has heard the liability question. Most of us answer it wrong. The real answer is not about insurance. It is about who was in the room when the tool was designed.
· 6 min read
Augmented Intelligence Is a Physician Problem. That Makes It a Physician-Developer Opportunity.
The AMA opened the door. Physicians must decide what to do with it. The survey data is not a comfort. It's a challenge. Here's what physician-developers do next.
· 9 min read
Skill Loss Is the Wrong Fear. Here's the Right One.
88% of physicians fear AI will erode their clinical instincts. That fear is real but misdirected. The greater risk is intellectual dependency on systems we didn't build and cannot interrogate.
· 8 min read
The AMA Is Right About Augmented Intelligence — They're Wrong About Who Should Build It
The AMA's 2026 survey shows 81% of physicians now use AI in practice. But read the fine print. Physicians want a seat at the table. The best way to earn that seat is to be the person who wrote the code.
· 9 min read
I Ditched Headless WordPress for Astro — Here's Why a Physician-Developer Should Too
After spending a day fighting a WordPress plugin that wouldn't respect a domain change, I rebuilt DoctorsWhoCode.blog from scratch with Astro and MDX. The migration took one afternoon. The clarity was immediate.
· 8 min read
From the ICU to the Marathon Course: What AI-Driven Glycemic Control Teaches Us About Athletic Performance
A physician-developer explores the powerful parallels between AI-driven glycemic control in the ICU and metabolic management for endurance athletes with Type 2 diabetes, introducing the Performance Glycemic Intelligence System (PGIS) as a real-world n-of-1 framework.
I Didn't Download an App. I Described My Problem to an AI and It Built One for Me.
A Maternal-Fetal Medicine specialist describes how his personal AI health system identified low HRV, recommended breathing exercises, and prompted him to build a custom evidence-based breathing app in a single afternoon. A case study in disposable software, physician agency, and the future of personal health technology.
· 9 min read
The Protocol-to-Website Industrial Complex:
By Dr. Chukwuma Onyeije, MD, FACOG | Maternal-Fetal Medicine Specialist & Medical Director, Atlanta Perinatal Associates
How I Built FGRManager: A Physician-Developer's Blueprint for Turning Clinical Protocols into Bedside Tools
It was a Tuesday evening consult. A doctor called with a patient at 31 weeks small for gestational age, elevated umbilical artery resistance, and a wo...
From Misinformation to Implementation: Why Modern Medicine Needs a Guideline-to-App Industrial Complex
Maternal-Fetal Medicine Specialist, Medical Director at Atlanta Perinatal Associates, Founder of CodeCraftMD
I Built an OpenClaw Agent to Understand What Developers Are Actually Doing (Not Because I Needed One)
Maternal-Fetal Medicine Specialist | Founder, CodeCraftMD | Atlanta Perinatal Associates
Part 1: The $50 Billion Bait-and-Switch
Maternal-Fetal Medicine Specialist & Founder, CodeCraftMD
Part 2: What We Should Actually Build
Maternal-Fetal Medicine Specialist & Founder, CodeCraftMD
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...
PGIS: When Medicine, Endurance, and Code Collide — Looking for Collaborators
I'm a maternalfetal medicine physician managing complex, high-risk pregnancies. I have long-standing type 2 diabetes. And right now, I'm training for m...
The Future of Clinical Documentation: A Practical AI Tech Stack for Physicians Who Code
> Keywords: AI clinical documentation, ambient transcription, EvidenceMD, CodeCraftMD, physician automation, clinical workflow, medical billing automati...
The Physician-Developer's FHIR Playbook: How to Pull Real Clinical Data from Epic Using Python
A step-by-step tutorial for physician-developers on authenticating with the Epic FHIR sandbox, making your first API call in Python, and building toward a SMART on FHIR clinical app -- no enterprise contract required.
· 14 min read