Search Interview Questions |  More than 3000 questions in repository. There are more than 900 unanswered questions. Click here and help us by providing the answer. Have a video suggestion. Click Correct / Improve and please let us know. |
|
|||
|
| |||||
| Core Java - Interview Questions and Answers for 'Clean code' - 1 question(s) found - Order By Newest | |||||
| |||||
| Ans. Modularity - First sign of good code is whether it has been segregated into methods and classes appropriately. I dont mind it in excess because I believe that is forward looking strategy as applications tends to expand and eventually become hard to read. Self Explanatory - Variables and methods should be named in a way that the code should be self explanatory even without comments. Use of Constant variables to explain use of literal. Proper Code Reuse - If there is anything being reused , it should be moved to parent classes / methods. Proper composition calls - Composed hierarchy should not be access in just single line. One or two levels is ok but having multiple levels make it hard to read and debug. | |||||
| Help us improve. Please let us know the company, where you were asked this question : | |||||
 Discuss Correct / Improve  code review clean code  Asked in 1 Companies  intermediate  frequent | |||||
 Related Questions | |||||
 Give an example of a time when you recommended code changes in a code review that simplified the code ? | |||||
| What are the scenarios you consider in code reviews | |||||
