flowchart TD
N1["Part 2. Why specification-based development"]
N2["Typical vibe-coding failures"]
N1 --> N2
N3["4. Hidden decisions. Important decisions remained inside the chat history and didn't make it into re"]
N2 --> N3
N4["5. Reviewer fatigue. The agent writes quickly, but the person gets tired checking a lot"]
N3 --> N4Diagram: Part 2. Why Specification-Driven Development
Lesson 5 of 5 in module «Part 2. Why Specification-Driven Development»
You are viewing the lesson without signing in. Sign in to save progress and take tests.
My notes
0 / 10000
Saved
Notes are saved in this browser. They will not appear on another device.
Course menu
Course
Specification-Driven Development with Qwen Code CLI
Progress
0 / 135
🔒
Reading: Part 9. Feature Validation: From Specifications to Facts
🔒
Study guide: Part 9. Feature Validation: From Specifications to Facts
🔒
Quiz: Part 9. Feature Validation: From Specifications to Facts
🔒
Flashcards: Part 9. Feature Validation: From Specifications to Facts
🔒
Diagram: Part 9. Feature Validation: From Specifications to Facts
🔒
Reading: Appendix A. How the Textbook Relates to Spec Kit and Kiro
🔒
Study guide: Appendix A. How the Textbook Relates to Spec Kit and Kiro
🔒
Quiz: Appendix A. How the Textbook Relates to Spec Kit and Kiro
🔒
Flashcards: Appendix A. How the Textbook Relates to Spec Kit and Kiro
🔒
Diagram: Appendix A. How the Textbook Relates to Spec Kit and Kiro