Module Check
This lesson closes Module 5 and the Building with AI track. It tests not only whether you can recall the facts and definitions from each lesson, but whether you can reason with them — applying them to new situations, weighing competing considerations, and thinking clearly about the responsibilities that come with being a builder in an AI-accelerated world. The six quiz questions below span the full module. After completing them, a capstone activity asks you to synthesize everything into a single, original artifact: a builder's commitment statement that you could realistically stand behind.
Flashcards — click each card to reveal the answer
A developer deploys a new version of her app while the old version is still handling user traffic. She routes traffic to the new version only after confirming it is healthy. This is an example of which deployment strategy?
A library you depend on releases a security patch for a critical vulnerability. You are aware of it but do not apply the patch for three months because you are busy with new features. A user is harmed by the unpatched vulnerability. Which concept from this module most directly applies?
A startup incorporates a library released under the AGPL license into their cloud service. AGPL is a strong copyleft license that applies even when software is accessed over a network. The startup wants to keep their codebase proprietary. Which statement is most accurate?
A student builds an app for a school and makes a text field that changes color from white to light yellow when users successfully submit a form. No other feedback is given. Which WCAG principle is violated, and why?
An AI coding tool generates a data processing function that accesses three database columns the developer did not request. The developer does not read the generated code and ships it. Which accountability principle does this violate?
A team ships a product with a known accessibility failure — a modal dialog that cannot be closed via keyboard — because fixing it would delay launch by two days. They disclose this limitation in their release notes. Compared to shipping without disclosure, which statement best characterizes the disclosed approach?
Every lesson in this module has been about a single idea: when you ship software, you enter into an implicit contract with the people who use it. You are telling them: I built this, I understand it, I take responsibility for it, and I will maintain it honestly. Copyright law, licensing, accessibility standards, deployment practices, and safety frameworks are all the infrastructure of that contract. Vibe coding lets you build fast — this module exists so that speed does not come at other people's expense.
Builder's Commitment Statement
- Write a personal Builder's Commitment Statement — a document of 300 to 500 words that you could realistically stand behind and post publicly. It should address the following:
- 1. Understanding: What is your commitment to understanding the code you ship, including code generated with AI assistance?
- 2. Safety and harm: What is your personal standard for assessing and mitigating harm before shipping? How will you apply threat modeling or equivalent thinking?
- 3. Accessibility: What minimum accessibility standard will you hold yourself to, and how will you verify it before release?
- 4. Licensing and credit: What is your practice for auditing dependencies, selecting licenses for your own work, and giving honest credit?
- 5. Accountability: What does accountability look like in your practice — how will users reach you, how will you respond to problems, and how will you decide when to maintain versus when to sunset a project?
- 6. AI assistance: Given that you work in an AI-assisted environment, what is your specific commitment regarding reviewing, testing, and taking ownership of AI-generated code?
- This is not a school assignment to be completed and forgotten. Draft it as if you would keep it and revise it as you grow as a builder. Exchange with a partner and give each other one honest piece of feedback.