Intro to Vibe Coding.

How to use AI, and build with it.

Today is in
two parts.

1

AI 101.

2

Vibe Coding.

What we’ll
learn today.

  • What AI is.
  • How to use it.
  • Why it’s useful.

Who typed into ChatGPT
or AI this week?

Camp 1

Scared of it.

Camp 2

All in.

Part 1 · AI 101

What is
this thing?

AI =
Artificial
Intelligence.

A marketing label. What it really is: statistics at scale, predicting what comes next.

So when you hear “AI,” hear very good guessing machine.

What it’s
not.

  • Not a brain.
  • Not conscious.
  • Not thinking.
  • Not a person.
It’s autocomplete
that read the internet.
That’s it.

Sentences.

Paragraphs.

Essays. Code. Legal briefs.

How AI learned.

Read
everything.

~10 trillion

Fill in the blank.

The cat sat on the ___

Humans
graded it.

Helpful.
×Rude.
×A lie.

It learned what good sounds like.

for the curious The name for this step: RLHF — Reinforcement Learning from Human Feedback.

It’s predicting
the next word.

for the curious One token at a time. No plan. No memory outside the current context window.

It’s not.

  • Searching the web live.
  • Thinking like you do.
  • Always right.
  • A person.

Where we are,
April 2026.

The
chart.

AI capability over time 2018 2020 2022 2024 2026 ChatGPT!

Nov 30,
2022.

ChatGPT.

100 million users in 2 months. Fastest app adoption in history.

Since
then.

2023See images.
2023Write code.
2024Talk to you.
2024Watch your screen.
2025Act on your behalf.
2026Work all day on a task.

What it can do.

A starting list. Pick one and open it today.

01

Draft a sympathy card

02

Translate what the doctor said

03

Plan dinners from your fridge

04

Decipher a legal letter

05

Prep for a hard conversation

06

Summarize a long email thread

07

Compare two job offers

08

Polish a cover letter

What it
can’t do
reliably.

  • Count things in a photo.
  • Do fresh math without a calculator.
  • Know what happened this morning.
  • Remember you next week.
  • Actually send the email.
  • Know when it’s wrong.
  • Tell you why it said what it said.
  • Count the R’s in “strawberry.” ← really
ChatGPT
Claude
Gemini

All three are very good.

Pick one. Don’t overthink it.

As of April 19, 2026.

ChatGPT

Best known. Good at everything. The one your coworker uses.

chatgpt.com

Claude

Great writing voice. Best for long documents and careful thinking.

claude.ai

Gemini

Tied into Gmail, Docs, Search. Lives where Google already does.

gemini.google.com

Strengths at a glance.

ChatGPT
Claude
Gemini
Best at
Creative range, plugins, images & vision.
Writing voice, long documents, careful reasoning.
Google integration, search, long context.
Weak at
Can sound generic. Sometimes overconfident.
Fewer integrations, smaller ecosystem.
Quality is inconsistent. Less creative voice.
Reach for it when
Brainstorming. General Q&A. Anything multimodal.
Writing. Analysis. Long reads. Tough decisions.
You already live in Gmail, Docs, or Search.

As of April 2026. This changes every month.

What does it cost?

All three have a free tier. Paid plans unlock better models and higher limits.

ChatGPT
Claude
Gemini
Free
$0
Basic chat, with ads.
$0
Small daily message cap.
$0
Works in Gmail, Docs.
~$20
Plus $20
Daily use. Most people.
Pro $20
Daily use. Most people.
AI Pro $20
Daily use. Most people.
~$100
Pro $100
5x more usage. Heavy use.
Max 5x — $100
5x more. Vibe coding.
~$200
Pro $200
20x usage. Power users.
Max 20x — $200
20x more. All-day coding.
Ultra $250
Top Gemini models, Veo video.

If you’re just starting: $20/month is plenty.

Open one of them
on your phone or laptop.

Try this exactly.

type this in
Explain [something you do at work]
like I’m 12 years old.

Now make it useful.

type this in
Draft a polite email declining
a meeting because I’m
double-booked.

Shrink something big.

type this in
[Paste a long article here.]

Summarize this in 3 bullets
a busy person can act on.

Use it as a sparring partner.

type this in
I’m deciding between [A]
and [B]. What am I missing?
Argue for each side.

Anatomy of a good prompt.

1

Role

“You are a copy editor…”
2

Task

“Rewrite this paragraph…”
3

Context

“It’s for a 5th-grade audience…”
4

Format

“Give me 3 options as a list.”

Careful!
It wants to agree with you.

AI is trained to be helpful. That makes it agreeable. Sometimes too agreeable.

Ask it “isn’t this a great idea?” and it’ll usually say yes.

Ask it “isn’t this a terrible idea?” and it’ll often agree with that too.

Don’t lead the witness.

Leading
“I’m taking this job offer. Don’t you agree it’s the right call?”
Neutral
“I have a job offer. Argue honestly for taking it. Argue honestly for declining. What am I not seeing?”

State facts. Ask for thought.

Leading
“My neighbor is being completely unreasonable about our fence. How do I handle them?”
Neutral
“My neighbor and I disagree about a fence. Here are the facts. What’s a fair way to see this? What might they be feeling?”

Before / after.

Follow-up: “Shorter. Friendly. From me to a coworker.”

Before
Dear Sir or Madam,

I regret to inform you that, due to a prior engagement on my calendar, I will be unable to attend the scheduled meeting at the designated time. I sincerely apologize for any inconvenience this may cause and appreciate your understanding in this matter.

Best regards.
After
Hey, sorry—I’m double-booked Thursday. Can we find another slot? Free most of Friday afternoon.

Go beyond an AI draft.

Pick one
from your
week.

A draft, a decision, a thing you don’t understand. Ask it.

5:00

Five minutes. Go.

Is it
alive?

No.

No body. No memory between chats. No feelings. No will of its own.

When you close the tab, it stops.

Will it
replace me?

Honest answer: it will change most jobs. End some. Create new ones.

The pattern so far: people who use it are outcompeting people who don’t.

Best move is to learn it, not avoid it.

Should kids
use it?

Yes, with rules.

Same conversation we had about Google, calculators, Wikipedia. Just earlier.

The rule that works:

It can help them understand homework. It shouldn’t do the homework.

When not
to use it.

  • Grief.
  • Medical diagnoses.
  • Spiritual counsel.
  • Legal advice you can’t have a human check.
  • Anything where being wrong matters and you can’t verify.

It lies
confidently.

It will cite books that don’t exist. Invent quotes. Make up case law.

for the curious At each step it samples a probable next token. No fact-check, no ground truth. Confidence is a side-effect, not a signal.

Verify anything
that matters.

Privacy.

  • Don’t paste SSNs.
  • Don’t paste client data.
  • Don’t paste medical records.
  • Don’t paste passwords. (ever.)

Don’t
outsource
your brain.

Use it to go faster, not to stop thinking.

If you can’t evaluate the answer, you shouldn’t ship it.

Starting
Monday.

  • Use it once a day for one week.
  • Try a second tool by Friday.
  • Follow one person who teaches this.

Ask it a question
you already know
the answer to.

DemoRunning in Qmelin park.

You now
know.

What it is.

Autocomplete trained on the internet.

What it’s great at.

Writing, thinking, summarizing.

Where it lies.

Anything specific, recent, or numeric.

How to drive it.

Role, task, context, format, follow-up.

You just used AI.

Intermission · Part 2 next

Vibe Coding.

10:00

Stretch your legs. Back in ten.

What I used
to do all day.

Senior designer. Week-long loop.

01
Understand the problem.
Interviews, notes, a wall of sticky notes.
02
Sketch, then Figma.
Wireframes. Flows. Revisions. More revisions.
03
Design reviews.
Feedback, iterate, present again.
04
Write a spec. Hand off.
Hope nothing gets lost in translation.
05
Wait. QA. Ship. Learn.
Weeks later, maybe.

What I do
all day now.

Same role. Same hours. Different loop.

01
Start with a half-baked idea.
Talk it out with Claude like a coworker.
02
Ask for a working prototype.
Real page, real code, in minutes.
03
Click, react, refine.
Critique the real thing, not a picture of one.
04
Ship. See what people do.
Same day. Sometimes same hour.
05
Design is a conversation.
I’m editing the product directly.

Part 2 needs
a desktop app.

The browser versions won’t run vibe coding. Download the real app first.

As of April 2026.

App
Mac
PC
Claude
ChatGPT
Gemini

Claude works on both. ChatGPT and Gemini are Mac-only for now.

Vibe Coding:
Talk to AI, get working software.

No syntax. No setup. Just words.

a curious thought Vibe coding is fragile. The AI can ship bugs it doesn’t notice, and code you can’t debug. Don’t run a business on it yet. But for prototyping an idea, it’s a superpower.

The new tools.

v0

Describe a page. Get a page.

Lovable

Describe an app. Get a live app.

Bolt

Full-stack, in your browser.

Cursor

An editor that writes code for you.

Claude Code

Ship whole features from a chat.

live demo

I’ll show you.

One sentence → a real page.

CueSwitch to Claude Mac.
If you already code

It’s a
teammate,
not a toy.

Claude Code and Cursor aren’t for toy apps. They work on real projects:

  • • Reads your whole codebase.
  • • Edits the right files.
  • • Runs your tests.
  • • Opens pull requests.

You review and steer. It does the typing.

What you could build
this week.

01

A personal portfolio

02

A family-recipes site

03

A weekend utility

04

A small automation script

05

A landing page for your idea

06

A birthday card website

07

An event RSVP page

08

A shared grocery list

Context windows.

How much the AI can read at once, in one conversation.

ChatGPT
Claude
Gemini
Free / Plus
~32K tokens
(about 70 pages)
~200K tokens
(about 500 pages)
~1M tokens
(about 2,500 pages)
Top tier
~272K on GPT-5.4
(about 700 pages)
1M on Max + Opus
(about 2,500 pages)
2M on Gemini 3.1 Pro
(about 5,000 pages)
When it forgets

Start a fresh chat. Old chats don’t help.

When it’s a big task

Break it into smaller chunks, one per chat.

When you paste a lot

Paste only what matters. Not everything.

Power tools,
when you’re ready.

Skip for now. Come back when Claude Code feels normal.

01

Subagents.

Spin up a smaller Claude to go research something in parallel, and report back.

parallel work
02

GitHub workflows.

Automations that run on your repo: tests on every change, deploys on every merge.

automation
03

Git worktrees.

Have two versions of your project checked out at once. Try risky changes without breaking the main one.

branching
04

Coding from your phone.

Claude Code runs on mobile too. Ship fixes from a coffee shop, or an airplane.

on the go
05

Talk, don’t type.

SuperWhisper or Wispr Flow turns speech into prompts. Faster than typing, once you get used to it.

voice input

Try it.

Open Claude (or any tool) and ask it to build something small. A page, a utility, a fun app.

Stuck? Raise a hand.

10:00

Ten minutes. Go.

Keep in touch

Hire me.
Or bring me
back.

I help teams use AI — as a designer, a speaker, or a vibe-coding partner.

Got an idea for another class? I’m wide open. Text or email.

Email
Web
joshuawold.com
Ideas welcome
  • A team workshop on AI at your company.
  • A deep-dive on vibe coding for non-engineers.
  • A 1:1 session to unstick a project.
  • Something I haven’t thought of yet.

Questions?

Thank you.

Keep going.

The full talk, my writing, and projects — all in one place.

joshuawold.com/ai
QR code to joshuawold.com/ai
Point your camera here.
Supplemental — reference

Claude Code,
step by step.

Section 1

How code
actually works.

1.A simple framework.

The whole web is just files in folders. Here’s the mental model.

1

A website in a browser.

You visit a site and see words like “Hello World” on screen.

2

Those words come from code.

The browser reads code files that tell it what to display.

3

Code lives in a folder.

Code files are stored in a folder, just like any other file on your computer.

4

Big sites = big folders.

Angel.com is one large folder, with smaller folders inside for each page.

5

Media lives in a database.

Videos and images sit in a database. The code just references them.

Section 2

Your first
Claude Code app.

2.Make a hello-world app.

Start to finish. You’ll need the Claude desktop app installed first (Section 3).

1

Create a project folder.

In Finder or File Explorer, make a new folder. No spaces in the name.

2

Open the Claude app.

Go to the Code tab at the top. Different from regular chat.

3

Connect your folder.

Click “select folder” under the chat box. Pick the folder you just made.

4

Give your instructions.

Type: “Make a hello-world website, fastest way possible.”

5

Set auto-accept edits.

Click the dropdown that says “Ask Permissions”. Change to auto-accept.

6

Hit enter — watch it go.

Claude plans, writes code, and builds your app.

7

Allow for session.

If Claude asks permission, pick “Always allow for session.”

8

Open the link.

Claude gives you a link. Paste it in your browser — hello, world!

+Bonus: the claude.md file.

A memory file for your project. Claude reads it every time, so you don’t repeat yourself.

1

What it is.

A plain-text file with context and instructions Claude should always follow.

2

What to include.

Your role, project goals, things to avoid (“never use emojis”, “I’m not a developer”).

3

Start from a template.

Copy a starter claude.md from a Google Doc. Paste into Claude Code.

4

Ask Claude to save it.

Say: “Make this my claude.md file.” Claude creates and stores it for you.

Section 3

Install the
Claude desktop app.

3.Get set up on your computer.

The web version of Claude can’t run Claude Code. You need the desktop app.

1

Go to claude.com/download.

Pick Mac or Windows. Click the button.

2

Download lands in Downloads.

Double-click the file. On Mac, you’ll see a popup.

3

Drag to Applications.

Drag the Claude icon into the Applications folder shortcut.

4

Open Applications.

Find Claude in your Applications folder. Double-click to launch.

5

Follow onboarding.

Sign in with your Angel Google account — not personal Gmail.

6

Answer “What do you do?”

Say you’re not a developer. Explain your role simply.

7

Pick a role description.

Choose the one that fits you best from the dropdown.

8

Go to the Code tab.

At the top of the app, click Code. This is where Claude Code lives.

9

Install Kode CLI tools.

When prompted, say yes. Takes 10–15 minutes. Keep your laptop plugged in.

10

You’re set up.

Switch to the Chat tab if you hit a snag — Claude can help debug.

Section 4

Connect GitHub.
Back up & share your code.

Why GitHub?

Cloud storage,
for code.

It’s what most developers use. Two jobs:

  • Back up your work. Roll back if something goes wrong.
  • Share with others. Build together on the same code.
Your code lives in two places
01

On your computer.

Local, private, on disk.

02

On GitHub.

Cloud backup, shareable.

Access GitHub on the web at github.com, or via the desktop app you download.

4.Back your work up to GitHub.

Five steps to get your project into the cloud.

1

Go to github.com.

Click “Sign up”. Create an account with your Angel Gmail.

2

Set up 2FA now.

Do this the moment GitHub prompts you. Use Google Authenticator. Skip it and you’ll get locked out of your own account later.

3

Pick your project.

Use an existing Claude Code folder, or create a new hello-world one.

4

Ask Claude to back it up.

“I have a GitHub account. Can you help me back up my project?”

5

Follow the instructions.

Claude walks you through it step by step. Project is now backed up.

Section 5

Share a project
with a coworker.

5.Work together on the same code.

Once your project is on GitHub, you can invite others to collaborate.

GitHub vs. fly.io — what’s the difference? Push to GitHub = back up your code so teammates can work on it with you. Your project isn’t public yet.  Push to fly.io = publish your app so people can actually use it (either inside Angel or on the open internet, depending on how it’s set up).
1

Back up to GitHub first.

Follow Section 4 before sharing. You need the project pushed.

2

Log in to github.com.

You should see your project listed on the left side bar.

3

Open project → Settings.

Click your project name, then the Settings tab at the top.

4

Click Collaborators.

Find it in the left sidebar. This is where you add people to the project.

5

Click Add people.

Opens a search box for finding coworkers.

6

Search by email.

Use their Angel email or GitHub username. They must already have an account.

7

Click Add [email].

Confirms the invite. GitHub sends it to them.

8

They accept.

Your coworker gets an email. Once they accept, you’re collaborators.