Chapter four is about writing comments. This chapter surprised me by saying comments are not typically a good thing. They make up for poor code that does not explain itself. This contradicts what I have learned throughout my few years coding here. I usually lose points on assignments if I do not add a great deal of comments explaining my code. This leads me to believe that my teachers do not expected us to write professionally when making our code. The chapter talks about using TODO comments. That is a practice that I have done when I know I will be taking a break from writing that part of the code with the intent of coming back to finish it. If you can avoid using comments by writing self explanatory code, then you should do so. However, when this isn’t possible, you should write short comments that explain what is happening in the code.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.

Chapter two was a very repetitive chapter. The main point of the chapter was to make sure you pick names for variables, methods, classes, and objects that make sense. The names should be understood by everyone and be easily distinguished from any other names used. The complexity of the names should also reflect the complexity of the variable or method.

Chapter three is about functions and how they should be simple yet effective. They should only do  one thing and have descriptive names that describe what that one thing is. You want your functions to be well organized so that they are easy to follow. You have to be willing to change your functions to keep them organized. You should make sure to have tests that pass no matter how you change them around.

These chapters are about keeping your code organized and easy to follow while still being functional.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.

This reading is about being professional. Being professional is necessary to better yourself as a software developer. The reading talks a lot about challenging yourself to spend your free time learn new skills or study up on old ones. It stresses that doing this will make you a better coder that will make the jobs of your colleagues and employers easier. It will help your career to be better at coding. I agree with this chapter because putting in a few hours every day for yourself will greatly improve your skills and make you worth more to future employers. It talks about making your code flexible and make sure to test your code often. You should change your code often to make sure it is flexible. By testing often you are able to catch more bugs and make yourself better at not making the same mistakes over and over again. Being professional is more than just doing your job, it is learning more skills to make yourself better.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.

Hello,

I am Christopher Hanson, a senior at Worcester State. I am starting this blog as part of an assignment for my senior capstone class. We are working with OpenMRS for our project and most of the posts will be about our progress on that assignment.

From the blog chanson2016 by chanson2016 and used with permission of the author. All other rights reserved by the author.