1 of 18

CSE 5 DISCUSSION / WEEK 5

Vibe Coding

Building with AI, one small idea at a time

Amisha Prasad

2 of 18

CSE 5 DISCUSSION / WEEK 5

What is vibe coding?

You describe the software you want in everyday language. AI generates code, and you try the result and request changes.

The term often describes building by conversation. In its original, narrower sense, it involves accepting code without reviewing it.

For this class, we will explore the workflow and practice checking what it produces.

3 of 18

CSE 5 DISCUSSION / WEEK 5

A brief history

Before the phrase

Code editors, templates, and visual builders already helped people create software.

2021

GitHub introduced the technical preview of Copilot, which suggested code inside an editor.

February 2025

Andrej Karpathy introduced the phrase “vibe coding.”

An ongoing debate

People use the phrase broadly. Careful AI-assisted programming also includes code review and testing.

4 of 18

CSE 5 DISCUSSION / WEEK 5

What happens behind the chat?

Your request

The model receives your instructions and available project context.

Generated code

It produces code based on learned patterns. This is inference, as in Week 3.

The tool

Depending on its permissions, an app may preview the result, edit files, or run commands.

Your decision

You inspect the outcome, test it, and choose what to change or keep.

5 of 18

CSE 5 DISCUSSION / WEEK 5

Why people find it useful

A starting point

Turn an idea into an early prototype with less setup.

Small custom tools

Try a quiz, timer, checklist, or simple data display.

Quick revisions

Explore changes to layout or behavior without rewriting everything yourself.

Learning support

Ask for explanations and compare what you expected with what the code does.

6 of 18

CSE 5 DISCUSSION / WEEK 5

The tradeoffs

Hidden mistakes

A polished interface can still calculate incorrectly or lose data.

Harder repairs

Fixing a problem is difficult when you cannot explain the code.

Ongoing costs

Hosting, paid services, and repeated tool use can add costs.

Human responsibility

Someone still needs to check privacy, accessibility, and reliability.

7 of 18

CSE 5 DISCUSSION / WEEK 5

A sensible first project

Example: a study timer that runs in your browser. It needs Start, Pause, and Reset buttons.

Begin with a personal prototype using made-up data and a small set of features.

Accounts, payments, sensitive records, and public deployment add responsibilities. Get experienced help before relying on those features.

8 of 18

CSE 5 DISCUSSION / WEEK 5

A clearer prompt for the timer

“Build a simple study timer for a beginner. Use one HTML file that opens locally in my browser, with no accounts, external services, or paid tools.

​

Include a 25-minute countdown with Start, Pause, and Reset. Repeated Start clicks must not make it count faster. Reset should stop it and restore 25:00.

​

Use clear labels and keyboard-accessible buttons. Explain how to open the file and give me five checks to try.”

Specify the goal, limits, and behavior you can check.

9 of 18

CSE 5 DISCUSSION / WEEK 5

The beginner workflow

Define

Choose one small task. Write down what success looks like.

Generate

Ask for the simplest version that meets those requirements.

Check

Try normal use, repeated actions, and unexpected inputs.

Revise

Save a working copy, change one thing, and repeat the checks.

10 of 18

CSE 5 DISCUSSION / WEEK 5

What should the timer do?

Start

It should keep one countdown at the normal speed.

Pause and resume

It should pause, then continue from the remaining time.

Reset while running

It should stop and return to 25:00.

Reach zero

It should stop at 00:00 without showing negative time.

11 of 18

CSE 5 DISCUSSION / WEEK 5

Common pitfalls

“Make it better”

Name the exact problem and the behavior you want instead.

Too many features

Add one feature at a time so you can identify what broke.

Random fixes

Report what you did, what happened, and what you expected.

No working copy

Keep a saved version before accepting a major change.

12 of 18

CSE 5 DISCUSSION / WEEK 5

A better debugging message

“I clicked Start twice. After 10 seconds, the timer had lost about 20 seconds. I expected it to lose about 10 seconds.”

“Explain the likely cause. Fix only the duplicate-countdown problem, keep Pause and Reset working, and tell me how to check the fix.”

The model’s explanation is a hypothesis. Rerun the checks before accepting the change.

13 of 18

CSE 5 DISCUSSION / WEEK 5

Privacy, permissions, and cost

Use dummy data

Keep passwords, private messages, and student records out of practice projects.

Protect credentials

An API key is a secret that can authorize access or spending. Never put one in public browser code.

Check actions

Understand file changes and commands before approving actions you cannot undo.

Check sharing

Confirm what becomes public, where data goes, and what services charge for use.

14 of 18

CSE 5 DISCUSSION / WEEK 5

Using AI to help you learn

Ask: “Explain what each part does in plain language. What happens when I click Start?”

Predict one behavior before running the app. Then compare your prediction with the result.

For coursework, follow the instructor’s AI policy. A generated explanation still needs checking.

15 of 18

CSE 5 DISCUSSION / WEEK 5

Class activity: improve the request

The vague request

“Make me a useful study app.”

With a partner

Choose one feature. Add two constraints and three behaviors you can check.

Possible checks

Try an empty input, a repeated click, or a page refresh. State what should happen.

Share one idea

Explain one detail your prompt now makes clear. No tool or account is required.

16 of 18

CSE 5 DISCUSSION / WEEK 5

Before sharing your project

Can you describe what it does, what data it uses, and what happens when something goes wrong?

Have you checked important actions, keyboard use, and the consequences of refreshing or closing the page?

A working demo is an encouraging start. Use stronger review when other people, private data, or money depend on it.

17 of 18

CSE 5 DISCUSSION / WEEK 5

What to take away

AI can lower the barrier to trying a software idea. You still choose the goal and judge the result.

Small projects and specific prompts make problems easier to find and changes easier to assess.

The useful skill is turning “it looks right” into “I checked what matters.”

18 of 18

CSE 5 DISCUSSION / WEEK 5

Sources and further reading

[1] Simon Willison (March 19, 2025)

Not all AI-assisted programming is vibe coding

simonwillison.net/2025/Mar/19/vibe-coding/

[2] GitHub (June 29, 2021)

Introducing GitHub Copilot: your AI pair programmer

github.blog/news-insights/product-news/introducing-github-copilot-ai-pair-programmer/

[3] GitHub Docs: responsible use and limitations

docs.github.com/en/copilot/responsible-use/inline-suggestions

Sources checked October 23, 2026. Classroom examples are original.