A system that breaks in unintended and unpredictable ways when simple changes are made is best described as exhibiting ____________.
The problem with trying to rush code is ____________.
The best way to deal with code rot is to ____________.
A major issue with deciding to redesign software is ____________.
When a system's code is hard to read, hard to change, and hard to understand, the system is best described as exhibiting ____________.
When you deliver many features initially, business expects ____________.
Bjarne Stroustrup said, "I like my code to be elegant and efficient; clean code should ____________."
Clean code ____________.
Brooks law states ____________.
When making changes to a system, fragility, inseparability, rigidity, and opacity make it difficult to craft accurate ____________.
New developers are mostly taught by.
The Sword Inc. programmers delivered too quickly because ____________.
According to Michael Feathers, "Clean code always looks like it was written by someone."
The process of separating modules is called ____________.
When you intend to go back and clean up messy code later, you are likely to clean it up ____________.
Review your answers, and click "Submit Exam" when you're ready. After submitting it, you'll be able to see how you did, review your answers, and submit any feedback you may have to us about our exam questions.