EMERGING TRENDS IN SOFTWARE ENGINEERING
DEVOPS
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Code that smells bad when viewed
|
|
|
Code that recognizes smell by itself
|
|
|
right on all counts
|
|
|
Code that is difficult to maintain in the future
|
Detailed explanation-1: -One or two letter variable names, non-descriptive function names, excessively adorned class names, and in worst cases using different naming schemes across the codebase, lead to this code smell. This makes code hard to read, understand, and maintain.
Detailed explanation-2: -Having code smells does not certainly mean that the software won’t work, it would still give an output, but it may slow down processing, increased risk of failure and errors while making the program vulnerable to bugs in the future. Smelly code contributes to poor code quality and hence increasing the technical debt.
Detailed explanation-3: -Code smells are usually not bugs; they are not technically incorrect and do not prevent the program from functioning. Instead, they indicate weaknesses in design that may slow down development or increase the risk of bugs or failures in the future.