Module Check
This lesson does not introduce new content. It asks you to demonstrate — through recall, reasoning, and application — that you have genuinely internalized the ideas across the nine lessons of this module. The questions span the full arc: what vibe coding is, what changed to make it possible, who it empowers and how, the honest division of labor between human and AI, the skills that remain essential, how to read generated code, how to stay in control, where the approach breaks down, and how to choose the right build approach for a real problem. Work through each section without rushing; precision matters here as much as it did in lesson 2.
Flashcards — click each card to reveal the answer
Which statement most accurately distinguishes vibe coding from using a no-code platform?
A prompt reads: 'Sort the list of students alphabetically.' What is the most significant flaw in this intent specification?
What is the most accurate description of what AI code generation is doing when it produces a response to a prompt?
A vibe coder builds three components separately — a user profile page, a notification system, and a data export function — each working correctly in isolation. When integrated, data does not flow correctly between them. What skill would have prevented this?
Using the build-approach decision framework, which dimension is most directly relevant to the concern that a healthcare app might violate HIPAA?
Why is 'the code runs correctly on my test cases' insufficient evidence of code correctness or security?
Every lesson in this module builds toward a single coherent position: vibe coding is a genuine paradigm shift that redistributes who can build and what they can build, but it does not eliminate the need for rigorous thinking — it relocates it. Syntax precision moves to the AI. Conceptual precision, systems understanding, honest evaluation, disciplined review, and sound judgment about fit and limits remain entirely with the human. The builder who masters these is a more capable builder in the age of AI, not a less capable one.
Capstone: Design a Responsible Build Plan
- Step 1: Choose one of the following project ideas, or propose your own to your teacher:
- Option A: A peer tutoring matching system for your school — students request help, tutors indicate availability, the system makes matches.
- Option B: A local neighborhood exchange app — residents post items to give away, others claim them.
- Option C: A personal finance tracker that imports bank transaction CSVs and categorizes spending.
- Step 2: Apply the full module's content to design a responsible build plan. Your plan must address:
- (a) Decomposition: list every sub-problem the system requires, with data contracts between components.
- (b) Division of labor: which parts will you prompt the AI for, and which decisions will you make yourself before prompting?
- (c) Risk assessment: apply all five framework dimensions; identify the top two risks.
- (d) Review gates: specify at what points you will perform code review, what you will check for, and how you will test.
- (e) Limits: identify any part of this project that exceeds standard vibe coding practice and describe what additional expertise or process would be required.
- (f) Intent specification: write the first three prompts you would send, fully specified — no vague instructions.
- Step 3: Present your plan to the class. Peer reviewers should identify: one strength of the plan, one gap or risk the plan did not address, and one question the builder should answer before starting.
- This is what responsible building looks like. The plan is the work.