Learning Paths

One destination. Three starting points.

Every path develops the same identity: a physician who can inspect, build, and take responsibility for software. The sequence changes because the starting work is different.

Path 1

Learn to Code

Build the habits and technical vocabulary required to turn a bounded problem into working software.

For
Physicians with little or no programming experience.
Outcome
Create, version, and explain a small project that solves one problem you understand.
1 course 4 lessons 27 min View path
Path 2

Use AI in Medicine

Move from isolated prompts to observable clinical workflows with deliberate human checkpoints.

For
Physicians who already use ChatGPT or another general-purpose AI tool.
Outcome
Design an AI-assisted workflow that protects clinical judgment, data quality, and accountability.
1 course 4 lessons 39 min View path
Path 3

Build Medical Software

Translate clinical rules and workflow knowledge into tested, deployable tools.

For
Physicians ready to build applications for clinical or operational use.
Outcome
Take a bounded clinical need from workaround to tested software with an explicit deployment boundary.
1 course 5 lessons 51 min View path

The Governing Principle

Read toward a build.

Articles become lessons when they have a defined place in a sequence. Lessons become a course when they produce competence. The project is where that competence becomes visible.

Help me choose a path