Chapter 4

I liked the author’s analogy about how when he first started typing he was not sure what keys he was pressing and once he got enough practice he was able to figure out what keys he was pressing without looking at it. When he pressed the wrong key he was able to recognize it without having to look at the keyboard. I think that same concept is true when working in the field. Once you get a lot of practice with coding in a language or a particular technology then you will be able to notice when you are making mistakes without even thinking twice about it. I also liked how you should be prepared for every scenario put out there. When a customer you are making software for wants something entirely different than what was initially planned then you should be prepared to make changes without having to stress much. I also liked how the author talked about how it is always a good idea to walk away from a problem when you are stressing too much about it. When you walk away you are able to relax and think much more clearly which at the end will help you produce and solve the problem you had to deal with from the start. I would personally take whatever the author said in this chapter and apply it in the workplace since a lot of it is proven and I have tried it and it works when performing any type of task.

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

Post from week 4/4-4/8

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.

OpenMRS Radiology: Difficulties

My team chose to work on a simple issue with the OpenMRS Radiology module. We had to delete unused lines from a couple of property files, this should have been an easy thing to do, but in order to know if the code was unused, we had to test it in the module itself. No one in our group had a completely working module, so we were unable to quickly finish this issue, and are still trying to get things working.

Our groups problems have made me learn a few things when it comes to outsourcing work to other teams. It is important to make sure the instructions for getting things set up are 100% accurate, and will work with any computer setup. If not, many people will be stuck on just the setup process like we have been in this OpenMRS project. Another important step is to include the system requirements for a project, if there are any. I am running on Windows Vista, which limits the versions of software I can download, and I don’t know if these older versions will be supported in the project.

When a project like OpenMRS expects college students, who have most likely little experience with similar work, to contribute to their project, they need to have directions for setup and submission that are refined to a classroom level. They do have the forum to post any issue we have, but this seems like a roundabout way to solve the problem, if someone keeps facing problem after problem, they will just be waiting for a response on the forum continuously. I hope we are able to get something done with this project before the end of the semester.

 

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

Radiology Module Update

This week I worked on an issue for the Radiology module in which I found dead and unused code that could be deleted to save space and increase efficiency. It might not be a difficult issue, but it helped me learn about the process of working on and testing an issue. There is nothing I would change about my process, fortunately everything went pretty well. I am in the middle of testing my edits, and I expect to receive working results as I searched for each line I was intending on deleting to see if it was used anywhere other than where it was initiated.

Overall, there were only 2 steps, but each step took a while to work on. Step 1 was just to search for each line in the messages.es file in the repository to see if it is needed or does absolutely nothing. If it is not used, just delete it. For safety reasons, I copied each line that was being deleted into another notepad file just in case we deleted a line that was actually needed. Second step is the testing to see if it still works. I am still in this process, but I will make another post that goes through the details of testing in the radiology module.

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

Radiology Module Update

This week I worked on an issue for the Radiology module in which I found dead and unused code that could be deleted to save space and increase efficiency. It might not be a difficult issue, but it helped me learn about the process of working on and testing an issue. There is nothing I would change about my process, fortunately everything went pretty well. I am in the middle of testing my edits, and I expect to receive working results as I searched for each line I was intending on deleting to see if it was used anywhere other than where it was initiated.

Overall, there were only 2 steps, but each step took a while to work on. Step 1 was just to search for each line in the messages.es file in the repository to see if it is needed or does absolutely nothing. If it is not used, just delete it. For safety reasons, I copied each line that was being deleted into another notepad file just in case we deleted a line that was actually needed. Second step is the testing to see if it still works. I am still in this process, but I will make another post that goes through the details of testing in the radiology module.

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

Wireless Connections and OpenMRS

This week, I continued work on the OpenMRS software, and continued trying to run OpenMRS from the puppet software. I’ve even tried reinstalling all the Git files for the OpenMRS Radiology system, including the puppet files for the dcm4chee servers. Even my teammates never saw the errors I’ve been getting, especially through the Windows command prompt, which is not UNIX-based.

Turns out running the software on a wireless connection makes the virtual box more likely to time out depending on how long vagrant’s timeout value is (I had it set to the default 300 seconds). I am going to try running the software on a wired connection next week. I’m hoping it all goes well.

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

Post from Week 3/28-4/1

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.

Chapter 4 and 5

In chapter 4 Martin mentions some rules and principles for coding. Coding needs concentration and focus. Whenever you are tired or distracted do not code. If you code in that situation the code will be wrong and sloppy. Also writing code when you are worry about something is not a good idea, so before writing code try to resolve the worry. Some programmers feel that they are more productive and infallible when they are in the “Zone”. The problem of writing code when you are in the Zone is that you lose some of big pictures. Writing code in the Zone is faster but it will cause you to go over that code again to make changes. One interesting thing that Martin mentions is about listening to the music while coding. Some programmers listen to music while coding and they think that they have more concentration. But music is helping them to enter the Zone. Factors such as sleep deprivation, fear, and depression can cause blockage. In that situations the solution is to find a pair partner. Working with someone can help you to think better. When you are stuck and feel tired just step away, go outside, take a shower and try to clear your mind from everything.

Chapter 5 is all about Test Driven Development(TDD). Martin believe that all programmers should use TDD in their codes. He mentions that first write a failing unit test before writing any code. Then writing code to make it pass and repeat this cycle ­­over and over until the final product is achieved. For me writing test before writing code is very hard. But I think doing this will help us to have fewer bugs in our codes. Also when we have bunch of tests that we trust, then when we see bad codes we can clean them without fear. But using TDD doesn’t guarantee that you won’t have bad code.

From the blog cs@Worcester – siminshamsblog by sshamsfallah and used with permission of the author. All other rights reserved by the author.

Post From Week 3/14-3/18

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.

OpenMRS Radiology Progress

For those that haven’t been keeping up with the blog, I joined the OpenMRS team as part of a class project. Over time, I have encountered some issues with the software.

3 weeks ago, Ivo, a member of the OpenMRS Radiology team from Austria, showed us how to run the OpenMRS software properly. I found the Skype tutorial somewhat interesting, and I figured I’d use his information to help me with the ticket we were given recently.

2 weeks ago, I started catching up to the rest of my team by installing the software necessary to install the OpenMRS Radiology code as well as the puppet software. Although I had no problems installing, part of the conflict for that Monday was mainly the wireless network and its slow download speed at the time.

Last week, I tried to run the puppet software through Vagrant and VirtualBox, the 2 programs I needed to run the software. Unfortunately, after about 2 minutes of getting the virtual machine running, the Vagrant software times out trying to boot. A discussion with a classmate and Dr. Wurst later, we thought my issue had to deal with the internet connection. I was running my PC on the school’s wireless connection at the time.

As soon as I got home that Friday, I tried running Vagrant again, only to have the software time me out again trying to boot the virtual machine. This time, I was running the software from my home’s wireless connection. I hope next week, if problems persist, I can try running the software on a wired connection. I’ll keep up to date next week.

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