The educator wing

Ready to build with AI?

Free, practical guidance for working critically, confidently and responsibly.

Why now?

  1. An extension of the oath

    I have always seen digital communication as an extension of my Hippocratic Oath.

    So I am happy to teach, train and up-skill when it comes to digital communication in the intelligence age.

  2. Long before AI

    Long before the current AI era, I believed that helping reliable medical information reach more people was part of my responsibility as a doctor.

  3. The benefits of broadcasting

    That belief led me from search and social media into mainstream media, where working with journalists and broadcasters taught me more about the rigour and discipline involved in communicating responsibly.

  4. A tectonic shift

    The way people find and process information is undergoing a tectonic shift. For years, organisations could expect people to discover their work through websites, search engines or social platforms.

  5. The collapse of traditional web search

    Increasingly, information is being summarised, interpreted and delivered by AI systems before someone ever reaches the original source.

  6. The space will not remain empty

    If credible experts do not learn to participate in this new information landscape, the space will not remain empty. It will be filled by increasingly automated content, often produced at scale and designed to capture attention rather than improve understanding.

  7. Risks of remaining silent

    Some of it exploits the parasocial relationship between an influencer and an audience, building trust in order to sell something further down the line.

  8. We have the skills

    People working in medicine and the life sciences already possess many of the skills this moment demands.

  9. they are transferable!

    We learn complicated and rapidly advancing science. We assess evidence, work with uncertainty, revise our conclusions and remain accountable for the decisions we make. Learning to use AI is another expression of that commitment to lifelong learning.

  10. The purpose

    The purpose of these lessons is not to persuade everyone to build a website in twenty-one days.

    It is to provide the scaffolding through which people across the life sciences can begin preparing now. When the need or opportunity arises, they should be ready to use these tools critically, confidently and responsibly.

  11. Why now

    We have an opportunity to help shape a new information ecosystem in which credible expertise remains discoverable and useful. If enough of us participate, the potential societal benefit for improving global health and well-being is immense.

The sessions

Where these questions came from, and where they are going: they began as one AI model's map of what a beginner asks. I am now testing that map against real readers, the people I teach and talk to, correcting it where it is wrong. The record shows the working.

What is this?

  1. What do I need to set up? The room, the folder and the habits a non-technical reader needs, using the Claude ecosystem as an example.
  2. Do I need to know how to code? No, not to start: this whole site was built by a doctor who never trained as a developer. What you cannot skip is verifying what the model builds, and that is the difference this session is about.
  3. What exactly is vibe coding with veracity? Vibe coding is building software by describing what you want to a model in plain language and reviewing what comes back; the veracity this site adds is the discipline that keeps the result trustworthy, and yours.

Can I do it?

  1. What is the best first project? The best first project is small, visual and about something you already know well, so you can check every word yourself. A one-page site, not an app: you stay the authority, and the model builds without becoming it.
  2. How do I write a good first prompt? A good prompt is not a secret form of words, it is a clear brief: what you want, what to reuse, what not to touch, and how you will check it. Six short fields, and none of them needs a clever phrase.
  3. What if the first version looks wrong? The first version being wrong is the normal start, not a failure. You do not scrap it: you say what is wrong, look at a few alternatives side by side, and keep the best. The taste and the veto stay yours.
  4. What if I get stuck in a coding loop? A coding loop is when each attempted fix returns you to the same fault, creates a new one or reverses the last change. The answer is not a more forceful prompt. Stop changing the code, name what you can actually see, ask for a diagnosis, and test one explanation at a time.
  5. How do I fix a bug without reading the code? Two real bugs on this site's signature design component were caught by looking at the page, not by reading the code; the four-step discipline that fixed them is one anyone can run.

Can I trust it?

  1. Is AI-generated code actually good? AI-generated code can be good, but "the page appeared" is not proof. Good code does the right job, survives checks, works on a phone, and can be changed without quietly breaking something else. You do not have to read every line, but you do have to ask for evidence and inspect the result.
  2. Is it really mine, and can I take it away? Ownership is not one switch. Your words, code, images, domain, accounts, third-party packages and AI output can each have different terms. Portability is simpler to test: keep the source in an account you control, download a complete copy, know which services it depends on, and prove that someone else could rebuild it.
  3. What I will not teach you yet, and why I will not teach a beginner to add logins, store private data, take payments or build a password system by asking an AI for one. Those features are possible, but their failures are hard to see and can harm somebody other than you. "Not yet" is a safety boundary, not a verdict on what you can eventually build.

Can I ship it?

  1. How do I get it onto the actual internet? Getting a vibe-coded site online is three things: a GitHub account for the code, a host that watches it, and a push. Knowing what a commit and a push actually do is the whole of the confidence.
  2. How do I update it once live? Changing a live site is two moves, not one: a commit saves the work, a push ships it, and on this site only the push goes live. Knowing which command is which is the whole of the safety.
  3. How long does it take, and what does it cost? AI can produce a first version in minutes, but the first version is not the finished work. Time is spent deciding, checking and refining; money may go on the AI tool, a domain and any services the site needs. A small static site can be inexpensive. Complexity and responsibility are what raise the bill.

Beside the climb

Going further

Method and craft sessions that sit alongside the numbered climb rather than on it. Reach for them when you want to go deeper; they are not steps you have to take in order.

Take it with you

Resources

Material to download and keep, alongside the sessions.

Something sparked your interest? Let's talk!