Clean Code Chapter 1

The first chapter of the book, “The Clean Coder” by Robert Martin had many interesting concepts and points for building elegant software. It had few interesting points regarding professionality and how being profession is very important for a software developer. The first point I found interesting was regarding the ideas on making our code more readable, reusable and versatile. I like the way how the author states, spending free times learning new skills will greatly improve our coding skills and builds a better career. He also states that the code should be cleaner, flexible and it should be tested often for better results. It was nice reading the chapter and being introduced to few points about professionalism. As most of us are in the senior year and will be facing the work environment in the future, I think learning good coding skills will help us to build good careers.

From the blog CS@worcester – pavanimothe by pavanimothe and used with permission of the author. All other rights reserved by the author.

Chapter 1 Reading

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.

Installing OpenMRS

The process of installing OpenMRS was a lot harder than I had expected.  The first step in the process was to just download that OpenMRS core from github.  This went exactly as expected but the next step is where somethings started to go wrong.  The first time that I tried to put the project into inteliiJ it had errors compiling.  Finally after a little trial and error I had corrected the errors that I needed to and it was time to move onto the next step in the process which was getting a maven clean install to run.  This process was a lot harder than it needed to be.  The first issue that I ran into was an error saying that my computer didn’t have enough memory to make a VM on the heap.  At first glance I thought that this was because my laptop is older and doesn’t have a lot of ram.  After doing a little research I found out that java was trying to take too much of my memory to run the process so after changing the default value the clean install was able to run.  After this it was time to run the Jetty run command to have the server start running.  Finally I was off to races and it was working.  The next step was installing my sql which was pretty easy to install.  Once this was done it was time to import the Legacy GUI.  The process went pretty easy just following the instructions.  After this it was time to go back into the LegacyUI and make sure that there were some entries in the database and there were!!!  Finally I was able to start coding for when we decide a project to work on!

From the blog CS@Worcester – dperry2blog by dperry777 and used with permission of the author. All other rights reserved by the author.

Installing OpenMRS

Let me start by saying this was a project within itself. Throughout the installation process there were multiple errors that took a fair amount of time to fix. The process started with installing IntelliJ. This was not much of an issue just a simple download. Then you have to clone the OpenMRS-core to your computer using git and add an upstream. This again was simple. You then needed to install Maven and a SDK. We were given directions to do this and the hardest part was changing the environment variables correctly. The next step was to do a clean install through Maven. This is where I ran into problems. It was coming up with an error with the sure-fire plugin. This error was caused by a Junit error. I ran a clean install that skipped this test and then it installed correctly. You could have also fixed this problem by opening your Open-MRS-core in IntelliJ and clicking on the build button. There will be errors in the code. You go to the Junit errors and do a quick fix and then run the maven clean install again and it should work. The next step was to run a jetty:run through maven. This also gave me an error because I did not have the jetty plugin. I looked up how to add the plugin and it involved adding code to the pom file of the project and updating a settings file. The directions were easy to find on google. You just had to find the correct spot in the code to add it. You then had to change your directory to the web-app directory and run jetty:run again. This time it will open a server and you go to http://loginhost.8080/openmrs. At this point you need to have MySQL, so you need to find a download on line and go through the installation process. You then follow the instructions to install the OpenMRS server. After the install you need to download the Legacy UI. After all of this OpenMRS is installed and ready to go.

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

The Clean Coder

I enjoyed reading the beginning of The Clean Coder very much. The Foreword in which the way that developers  are treated by management is highlighted rang true with my own personal experience. The Foreword also laid out the main theme of the book and gave a great purpose for continuing reading. The Preface was also very powerful, and displayed how management ignores the technical experts with dire consequences. The Pre-Requisite Introduction gave a good introduction to the author and his background. The most powerful part of the reading in my mind was in Chapter 1 where the author said that QA should find nothing, and that bugs making it to QA should be just as embarrassing as bugs making it to production. The emphasis on extensive testing and automated tests had an impact on how I do my software development. I enjoyed reading the beginning of The Clean Coder and look forward to continuing reading.

From the blog cs-wsu – Spencer Leal by spencerleal and used with permission of the author. All other rights reserved by the author.

Clean Coder ch2

This chapter was very hard to read because I am not a confrontational person. I would rather become a sleep deprived, caffeine addicted, overworked person for a few weeks than tell my boss no. I may argue here and there with people on the same field as me, but anyone put in authority over me is to be heeded to. I would absolutely be one of the people saying, “I will try”. I am not sure how much I could change in this aspect, being friendly with others is my personality, and I am not sure I would want to risk changing that. In the instances provided in the text, I can see why and how it is useful to say no, but it would take a lot to get me to that point. This chapter was filled with useful points and examples, and probably contains the most important information that I needed to hear.

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

Clean Coder ch1

Overall, the first chapter of the book “The Clean Coder” had a lot of useful insights and lists of useful information, as well as good ideas for self-improvement. There were a few minor things I disagreed with such as always writing tests first, and testing every single line. While parts of these things are useful, actually writing the tests first is not always the best thing, and testing every line is ideal but often unnecessary unless coding in a basic environment. His point about spending time outside of work on practice is a good idea, though hard to follow. I think it is great that he talks about owning your work and the responsibility that comes with it. I do not know if I would pay a company $10,000 for a mistake I made, but the reasoning was not lost on me. Professionalism is definitely something I must work on.

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

Clean Coder ch2

This chapter was very hard to read because I am not a confrontational person. I would rather become a sleep deprived, caffeine addicted, overworked person for a few weeks than tell my boss no. I may argue here and there with people on the same field as me, but anyone put in authority over me is to be heeded to. I would absolutely be one of the people saying, “I will try”. I am not sure how much I could change in this aspect, being friendly with others is my personality, and I am not sure I would want to risk changing that. In the instances provided in the text, I can see why and how it is useful to say no, but it would take a lot to get me to that point. This chapter was filled with useful points and examples, and probably contains the most important information that I needed to hear.

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

Clean Coder Chapter 1

Robert C. Martin’s book  Clean Coder: A Code of Conduct for Professional Programmers reviews the basics of being a professional programmer in chapter 1. Some of the important key points are being responsible for all your work, making sure your code is the highest quality you can manage, always test your own code, and being aware of more than just the code. Martin gives a great introduction to being a professional for anyone that is not quite sure what it truly means to be a professional programmer. I personally did not think this was that useful of a chapter though because most people know what being a professional is, it is just the matter of applying yourself to succeed at it. We will see what advice Martin gives in the next few chapters in my next Clean Coder post.

From the blog cs-wsu – mmoussa7wsu by mmoussa7 and used with permission of the author. All other rights reserved by the author.

Clean Coder ch1

Overall, the first chapter of the book “The Clean Coder” had a lot of useful insights and lists of useful information, as well as good ideas for self-improvement. There were a few minor things I disagreed with such as always writing tests first, and testing every single line. While parts of these things are useful, actually writing the tests first is not always the best thing, and testing every line is ideal but often unnecessary unless coding in a basic environment. His point about spending time outside of work on practice is a good idea, though hard to follow. I think it is great that he talks about owning your work and the responsibility that comes with it. I do not know if I would pay a company $10,000 for a mistake I made, but the reasoning was not lost on me. Professionalism is definitely something I must work on.

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