A group of developers pulled together for a redesign is.
When the various parts of a system cannot be independently reused in some other system, the system is best described as exhibiting ____________.
The problem with trying to rush code is ____________.
The principle that you should always check-in code cleaner than it was when you checked it out is known as The ____________.
When you intend to go back and clean up messy code later, you are likely to clean it up ____________.
A system that breaks in unintended and unpredictable ways when simple changes are made is best described as exhibiting ____________.
Bjarne Stroustrup said, "I like my code to be elegant and efficient; clean code should ____________."
According to Ward Cunningham, "You know you are reading clean code when ____________. "
When making changes to a system, fragility, inseparability, rigidity, and opacity make it difficult to craft accurate ____________.
The productivity trap begins with ____________.
Clean code ____________.
Doubling the number of programmers on a project.
Brooks law states ____________.
You should clean up bad code ____________.
The process of separating modules is called ____________.
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.