This week we finished RAD-58 and found out it had already been completed so we started RAD-235. This issue has to do with the modality of the radiology machine. Ivo wants them called a different way. On Wednesday we believed we completed the issue. On Monday we will discuss as a group if we think our issue has been solved. If we agree that it has been we will send a pull request and submit our solution. Hopefully it will be accepted. I am assuming that if it is accepted or while we are waiting for it to be accepted we may start on a new issue if we determine we have enough time.

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

This week our group fixed the RAD-58 issue. We still need to follow the steps to get the change approved and committed. This will be done next week once we ask Ivo some questions about JUnit tests. I also made progress with Dana getting the environment set up on his desktop so that he doesn’t have to work on my computer.

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

This week was a successful week. I got a VM running without the radiology module. I then installed the radiology module and got a new VM working with it. I have started working on issue RAD-58 while also helping my group with their installation process.

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

This week I installed the 12 modules. I moved the ports around so that when I did vagrant up it worked again. The next step is to install the radiology module and then I will be able to work on our issue.

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

This week I have gotten openmrs working through vagrant. I have installed a JDK and Maven so that I can install the modules. This weekend I am going to start installing the modules so that I can start working.

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

I did not make much progress on getting vagrant up and running. I now have a 404 error when trying to open localhost:8080/openmrs/. I am still trying to get it up and running so that I can work on my project.

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

This week I read all of the chapters from clean coder and wrote blog posts for each. I have started The process of installing vagrant. I’m running into an error with mySQL. I’m going to install all of the requirements we needed at the beginning of the semester with the hope that I install something that I need to get vagrant to work. I get the error after running the vagrant up command in the git bash terminal. I hope to get this issue resolved be next week.

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

This was a short chapter about TDD. TDD is where you write your tests before the code that is tested. You develop the tests alongside your code instead of after it. This forces you to write code with more structure and to write better code overall. It is not fool-proof, but it does help. It helps you change your code because you know there are tests for all of your code already, so you know when you break your code. The tests will make sure that you know what you want your code to do and will help third parties follow your code. I think TDD works well but I know I need more practice with it. I plan on using it throughout my career.

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

Chapter four starts off by telling you to never code when you are tired. Coding is difficult and if you are not focused, your best work will not be done. It then tells you to find a way not to think about personal things that are worrying you. This comes back to the same principle: if you are distracted, you can’t code well. The chapter then talks about “the zone.” I have coded in the zone and it does put out code faster but the chapter says that while you may be coding faster, you may not be coding better. It then talks about music and how it can help some people but it hinders most. I do like to listen to music when I code because it helps me shut out the world. However, as the chapter states, this may just be putting me in the zone, which is where I don’t want to be. The chapter talks bout working in pairs to solve most of the issues one may have with coding. You won’t enter the zone, if you are stuck they can help, and they can stay on task while you help someone else. You need to prepare your mind and body to write code. You need to be well rested and disengaged from your problems. You also need to know when to take a break from your code and re-energize. Following these steps will help you write better code while also giving you better estimates on how fast you can write code.

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

These chapters together are about communication. Chapter two wants the professional coder to say no when there is no other option. A professional needs to say no when they can’t get something done. However, in chapter three, it talks about the importance of saying yes if it is within your abilities to do so. Either way you must be definitive with your answer. An “I’ll try” is not acceptable. If you can’t do something say you can’t do it, and if you can do something, make a commitment to get it done.

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