Your AI questions answered
- 1. How do I get strong AI output (not generic slop)? → Talk #1
- 2. Can AI help even where I'm the expert? → Talk #2
- 3. Where do I start when it feels like it's already too late? → Keep Learning (it's actually a great time to begin)
Using AI to Reach Gen Z
Understanding how Gen Z thinks about feedback and AI is essential for effective communication. This generation brings unique attitudes shaped by growing up with technology—but that doesn't mean they automatically embrace AI.
Concept #1 Give AI Context materials to improve output
Concept #2 Use AI to reframe from different perspectives and frameworks
View Talk #1 Learning GuideAI and Radiology Residency
What Program Directors should keep in mind
Use AI as a strategic thought partner that can engage with you through every phase of your work. This collaboration can be used as Co-Thinking and Co-Working.
View Talk #2 Learning GuideWhat to Try Now
Start with a problem. Try to solve it. This is very motivating.
(Not: "I have a hammer, now where's the nail?")
Ask AI how to start. Ask AI to explore options.
Ask AI when you hit a road block.
Be Inspired
How to master AI Powered Creativity in just 13 minutes - Jeremy Utley
youtube.com/watch?v=wv779vmyPVY
You're Not Behind (Yet): How to Learn AI in 17 Minutes - the MIT Monk
Try These First
Stanford's Practical Guide to 10x Your AI Productivity | Jeremy Utley
youtube.com/watch?v=yMOmmnjy3sE
The 3-Step Method That Makes ChatGPT, Claude & Gemini Finally Match Your Standard
youtube.com/watch?v=FkR-1Qol8PI
I Ranked Every AI Feature by How Useful It ACTUALLY Is
youtube.com/watch?v=8w4ZH73z97g
The Only AI Tools You Need (Part 1 - Daily Use)
youtube.com/watch?v=htZRCE2GgIs
The Only AI Tools You Need (Part 2 - Productivity AI Tools)
YouTube Channels
Great for examples to try out yourself. Frequent new videos. Very up to date.
Dylan Davis
Jeff Su
Matt Maher
RoarTechEdu
Newsletters
Less often. Big picture. Thoughtful.
Ethan Mollick
Jeremy Utley
Just Fun
Try Google Labs. It's AI "toys." Each one you can figure out in one minute and produce something in five minutes. Each one you can easily tinker with the design, if you want, to make into something you really want. The process of playing will teach you about how AI can work.
Google Labs
Vibe Coding - If You Are Ready to Start
Claude Cowork
Desktop tool for non-developers to automate file and task management
youtube.com/watch?v=rdURhrS4xHIOfficial "Claude Code in Action" Course
Anthropic's official training course for Claude Code
anthropic.skilljar.com/claude-code-in-actionGod of Prompt: Claude Cowork Deep Dive
Comprehensive guide to mastering Claude Cowork
godofprompt.ai/blog/claude-cowork-complete-guideLeon Van Zyl
youtube.com/@leonvanzylRay Amjad
youtube.com/@RAmjadNic Conley
youtube.com/@niconleyHow to Vibe Code This Study Guide
How to build a site like radiologycraftapp.com using Claude Code, GitHub, Vercel & VS Code.
This is a condensed roadmap—not a click-by-click tutorial—for building and deploying a professional website using AI as your primary developer. It is written for professionals who are comfortable with AI chatbots but have little to no experience writing code in a terminal or using developer tools.
The approach works for both static HTML sites (a simple page or set of pages with fixed content, like a teaching hub or portfolio) and dynamic web applications (sites with interactive features like quizzes, calculators, or forms). The workflow is identical—you describe what you want in plain English, and the AI builds it. The only difference is what you ask for.
All the know-how and step by steps are in these two videos:
First, Watch Alex Finn
The only Claude Code guide you'll ever need (Opus 4.5) — 25 mins. This YouTube walks through how to install Claude Code, use a Terminal like VS Code (free), GitHub (free) and Vercel (free). It takes you all the way from setup to building and installing a website in a professional way.
youtube.com/watch?v=UVJXh57MgI0
Second, Watch Dylan Davis
I Stopped Using PowerPoint Once I Learned This Claude Method — 20 mins. This YouTube walks through how to build a modern clean looking presentation in HTML (web browser based). Note, use VS studio Code (free, set up decribed in first video below) instead of Cursor.
youtube.com/watch?v=TZ3yYXAz_i8You are the director. The AI is your engineer. You describe what you want, review what it produces, and approve or redirect. The AI writes code, runs commands, and fixes its own mistakes. You do not need to understand the code it writes—you need to understand whether the result matches your intent.
When something breaks—and it will—you copy the error message, paste it into the AI, and say "explain what went wrong and fix it." A broken build is not failure. It is a normal part of the conversation between you and your AI engineer.
This error-paste-fix loop is the single most important skill in vibe coding.
Claude Code requires a subscription. GitHub and VS Code are free. Vercel has a free personal tier—plenty for this use.
VS Code
A free code editor from Microsoft. This is your workspace. It has a built-in terminal (a command-line panel at the bottom of the window) where you will type commands. Open it from the top menu: Terminal → New Terminal.
Claude Code
Anthropic's command-line AI coding tool. After installing Node.js, you install this by typing npm install -g @anthropic-ai/claude-code in your VS Code terminal. It requires a paid Anthropic account or API access.
GitHub CLI
A command-line tool for GitHub (where your code is stored and versioned). Create a free GitHub account, install the CLI, then run gh auth login to connect it.
Vercel CLI
The hosting service that puts your site on the internet. Create a free Vercel account, then install the CLI by typing npm install -g vercel and run vercel login.
If any of these installations give you trouble, paste the error message into Claude (the chatbot, not Claude Code) or ChatGPT and ask it to walk you through the fix for your specific operating system. AI is excellent at troubleshooting setup problems.
The entire process follows five phases. Each phase is a natural checkpoint—finish one before moving to the next.
Phase 0 — Plan Before You Build
AI performs dramatically better with a clear brief than a vague prompt. Before opening Claude Code, write out your answers to a few foundational questions: What is this site's purpose, and who is the audience? What are the main pages or sections? What tone do you want—clinical, casual, authoritative? Are there existing sites whose look and feel you admire?
You can use any AI chatbot to sharpen your thinking. Open Claude Code in your VS Code terminal (type claude) and paste your notes with the instruction: "Help me turn these notes into a clear project brief for building a website." Claude is a planning partner before it is a builder.
Phase 1 — Capture the Design
Instead of trying to describe a visual style from scratch, point Claude at a website you like. In Claude Code, say something like: "Visit [URL] and write a file called STYLE_GUIDE.md that captures its visual style, typography, spacing, color palette, and content tone. Save it to my project folder."
This style guide file becomes your design "lock." Paste its contents at the beginning of every new Claude Code session to maintain visual consistency. AI models can drift aesthetically across sessions; the style guide prevents that.
Also ask Claude to generate a REQUIREMENTS.md listing every page, section, and feature you need to build. Read these documents carefully. Fixing the plan at this stage costs nothing. Fixing it after three pages are built is frustrating.
Phase 2 — Build One Page at a Time
Never ask the AI to build the whole site at once. Start with one page (usually the homepage). Tell Claude: "Build the homepage only, following REQUIREMENTS.md and STYLE_GUIDE.md. Run the dev server when done and give me the local URL."
Open that URL in your browser to see the result. Review the page and give feedback in plain English: "The header is too large," "I want the nav links right-aligned," "Change the background to a lighter grey." Approve the page, then move to the next one.
Keep structure and content as separate steps—build the layout first with placeholder text, then fill in your real content in a dedicated pass. This protects your layout from accidental changes.
Key tip: Press Shift+Tab inside Claude Code to enter Plan Mode. In this mode, Claude outlines what it intends to do before writing any code, giving you a chance to approve or adjust the approach first. This is especially valuable early on.
Scaling to interactive features: When you're ready to add a quiz, a calculator, a branching clinical case, or any other interactive tool, the workflow is identical. Describe the interaction in plain English. The same site can host these features as embedded components. You do not change your process—you change what you ask for.
Phase 3 — Deploy to the Internet
Once your pages look right locally, tell Claude Code to handle deployment. The sequence is three commands in plain English:
1. "Initialize a git repository in this project folder."
2. "Create a new GitHub repository called [your-site-name] and push all code to it."
3. "Deploy this project using the Vercel CLI."
Within minutes, Vercel gives you a live public URL. From this point forward, every time you push a change to GitHub, Vercel automatically redeploys your site—no manual steps needed. You can later add a custom domain through Vercel's dashboard if you wish.
Phase 4 — Maintain and Iterate
Your site is now live, version-controlled, and auto-deploying. To make changes, open the project folder in VS Code, start Claude Code, paste your STYLE_GUIDE.md to re-establish context, and describe what you want to change. Claude makes the edits, you review in the browser, and when you're satisfied, tell Claude to commit and push. Vercel handles the rest.
Three prompts solve the vast majority of problems:
For error messages: "Here is the exact error: [paste]. Explain what happened and fix it."
For visual issues: "The page doesn't match the style guide. Here is what I see: [describe]. Correct it."
For lost context: "Here is my STYLE_GUIDE.md and REQUIREMENTS.md. Remind yourself of the project and tell me where we left off."
The deeper principle is this: AI is not only your builder, it is also your debugger, your explainer, and your planning partner. When you encounter something you do not understand, ask the AI to explain it before you ask it to fix it. Over time, you will absorb vocabulary and concepts naturally, without ever needing to take a formal programming course.
Change one thing per prompt. Adjust spacing, or change a color, or restructure a section—but not all three at once. If Claude "improves" the design in ways you did not ask for, respond: "Revert to the style spec. No new design elements."
Small, incremental prompts keep you in control and make it easy to undo a bad change.
What matters to you
Why should you specifically care about this?
What are the AI advances creating recent headlines?
What AI means for our future work, identity, society?
What are responsible use and needed guardrails?