tailieunhanh - 13 Clarity and Maintainability CERTIFICATION OBJECTIVE • Writing Clear and Maintainable

13 Clarity and Maintainability CERTIFICATION OBJECTIVE • Writing Clear and Maintainable Code 2 Chapter 13: Clarity and Maintainability CERTIFICATION OBJECTIVE Write Clear and Maintainable Code Now that you’ve made your code readable, does your easy-to-read code actually make sense? Can it be easily maintained? These are huge issues for the exam, worth a very significant chunk of your assessment score. We’ll look at everything from class design to error handling. Remember that you’re a Team Player. Some key areas of code clarity are covered in more detail in the Documentation chapter, so we won’t discuss them here. Those areas include the importance of meaningful comments and self-documenting identifiers. The. | JAVA 2 SUN CERTIFIED PROGRAMMER DEVELOPER 13 Clarity and Maintainability CERTIFICATION OBJECTIVE Writing Clear and Maintainable Code 2 Chapter 13 Clarity and Maintainability CERTIFICATION OBJECTIVE Write Clear and Maintainable Code Now that you ve made your code readable does your easy-to-read code actually make sense Can it be easily maintained These are huge issues for the exam worth a very significant chunk of your assessment score. We ll look at everything from class design to error handling. Remember that you re a Team Player. Some key areas of code clarity are covered in more detail in the Documentation chapter so we won t discuss them here. Those areas include the importance of meaningful comments and self-documenting identifiers. The issues raised in this chapter are General programming style considerations Following OO design principles Reinventing the wheel Error-handling General Programming Considerations The coding conventions covered in the previous chapter are a great starting point. But the exam is also looking for consistency and appropriateness in your programming style. The following section lists some key points you should keep in mind when writing your perfectly-formatted code. Some of these will be explained in subsequent sections several of these points are related to OO design for example and we cover them in more detail in that section. Once again this is no time to debate the actual merits of these principles. Again imagine you ve come into a project team and need to prove yourself as a what Yes Team Player. The first thing the team is looking for is whether you can follow the conventions and standards so that everyone can work together without wanting to throw one another out the seventh floor window and onto the cement fountain below. Unless you re a dot-com company and your office now looks over an abandoned gas station. These points are in no particular order so don t infer that the first ones are more important than the last. You can .