Healthcare CIO · CTO · AI Practitioner
Practitioner AI: building real things, documenting what works, and sharing what I learn — because the most useful AI voices belong to experienced practitioners.
About
I spent my career as a healthcare CIO — leading technology strategy across some of the largest diagnostic and health system organizations in the country. Along the way I learned that the best technology decisions come from people who understand both the problem and the tools.
That belief is what drives my current focus on AI. Not the hype. Not the theory. The practice. I am building real things, documenting what works, and sharing what I learn — because I think the most useful AI voices right now belong to experienced practitioners, not just technologists.
My AI journey began with a simple question: can I actually build something useful without a development team? The answer turned out to be yes — but only once I started thinking like a builder instead of a user.
Career highlights
Projects
Instant Pot Doc
Converts stovetop recipes for electric pressure cookers. Strict state machine flow, fill limit safety, ingredient substitutions, smart scaling. Built without a developer.
Full story → ● Livedavidsevans.com
another AI journey
This site. Built by briefing Claude with a structured document, then iterating in a single session. A demonstration that the process works on its own terms.
Full story →At Hand
A task management app for Apple, built using vibe coding on Base44. Currently in testing and preparing for Apple App Store submission.
Coming soonPractitioner AI
A weekly series documenting what it looks like to actually build AI tools — not as a developer, but as an experienced executive who decided to figure out what works. Posts publish weekly, Tuesday or Wednesday morning.
The Origin Story
How a practical experiment with recipe conversion became a lesson in AI consistency — and the beginning of a larger journey.
The Victory Lap That Wasn't
Prompt drift, ChatGPT diagnosing its own ceiling, and the moment I realized I needed a different tool.
The Pivot
I brought everything I had built to a different AI. What happened next surprised me.
I Asked AI to QA Itself
The tool was live. But had I actually solved the consistency problem?
The Governance Question
AI needs the same discipline any well-run project needs. Prompt engineering turns out to have more in common with writing good requirements than writing code.
The Wrap
Three layers, one recipe converter, and why AI is not an unattended panacea. Next up — vibe coding.
Contact