Tag
12 posts
Markdown is not just a writing format. For physician-developers, it is the connective tissue between clinical thinking, documentation, GitHub, AI workflows, and build-in-public learning.
A beginner-friendly guide to turning a spare computer into a focused Omarchy workstation for Git, containers, AI coding agents, and small clinical software projects.
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.
I built a pipeline that turns any email into a tagged Markdown note in my Obsidian vault, using nothing but Gmail, Apps Script, and the GitHub API.
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.
A practical path for physicians who want to move from GitHub basics to building real medical AI projects.
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.
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.
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.
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.
Most physician-developers lose code the same way: no backups, no history, no way to recover. Here is why version control matters.
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.