OpenMRS-Radiology Module Setup

I am using an old Windows Vista laptop, with very little memory, so I did not expect the Vagrant and Virtual Box to run properly. I tried to set it up regardless but got errors, I tried to fix them but I think it is just not going to work. I will still be able to work on this projects coding, but I will have to rely on someone else or another device in order to test my code on the module. I wish there were system requirements in this modules tutorial, so I could know if my system is the issue or something else I am doing wrong. This taught me how important it is to have good instructions for users in tutorials, and to include every piece of information they will need in order to run it. Moving forward, I might attempt to get it working, but I want to work on the module as well, and actually get work done, so we will see how far I get.

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

Clean Coder Chapters 2 and 3

I have recently read more of The Clean Coder, and what I find interesting is that the two chapters I read talk about polar opposites when it comes to clean coding in the software world. There are other tips in the chapters that I find interesting, and I’d like to share some of these tips and how they relate to my beta testing experience, if applicable.

Chapter 2 was all about Saying No and how to say it properly. However, what i found interesting and important was that not only does one have to defend their No answer, but there’s a way to find the best possible outcome. The example described in the book shows how an issue over a dysfunctional login page turned into the best possible outcome: a mock-up that doesn’t actually check the username-password combination, but one can still log in. This I find is a more appropriate approach to defending a No answer for the reason that the program that was expected wasn’t ready at the time.

Chapter 3, however, talked about how saying Yes produces the right result. One scenario I found interesting is the scenario in a conversation between a manager and her employee who is responsible for modifications to a rating engine. As the scenario progresses, the book talks about how to improve the situation, by not saying “try” and committing to the task. The situation also carries some “what-ifs” in-between. For example, “What if this happened” and “what if that happened”. The conversation between developer and manager gets really interesting as the read continues.

This book is already interesting as it is. I hope to read more of The Clean Coder soon.

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

Practice, Practice, Practice

Chapter 6 of “The Clean Coder” primarily focused on practice. Martin explained the different types of practice including Kata(practicing on individual skills), Wasa(practicing in pairs with another person), and Randori(free-form practice). With these three sets of practice techniques he compares each to martial-arts. He states that much like martial-arts, you will never get two exact sets of problems(or opponents) and you don’t practice against a particular style, but instead practice technique so you know how to handle each unique situation. By practicing how to break down and tackle these problems, when one appears you know which direction to take to assess it.

I am sure when Martin first began practicing, his sources were limited. In today’s technology age, there is an abundance of sources to practice skills such as online sites like LeetCode, Project Euler, etc. and even open-source projects you can contribute to on github. The best type of practice is your own personal projects because you experience the entire software engineering process from gathering requirements, to development, and even testing. No matter how you practice, as long as you do it you should be fine. Even Michael Jordan, the greatest basketball player of all time spent his time in the gym practicing his craft. Software Development isn’t any different in that sense.

From the blog CS@worcester – My Progression as a Developer by xg2016 and used with permission of the author. All other rights reserved by the author.

Test Driven Development

Test Driven Development(TDD) was the topic of chapter 5. TDD was explained as a continuous cycle of writing a test for code designed to fail at first, then writing just enough code to make it pass. These cycles repeat over and over until the final product is achieved. The purpose of this development method is to ensure we are writing code that can easily be maintained. You won’t have to worry about introducing something in your code which breaks it horribly and you can’t pinpoint the reason for it. If you write code and all of your tests fail, you know exactly where the bug was created and this simplifies the debugging process because you won’t have to search through thousands of lines of code to fix your problem.

TDD is a different process than what you do when you are first programming. At first you build an entire project and test after to make sure your program outputs exactly what you want. The fault with this method is you design tests around what you expect to happen, and you don’t take into consideration all of the possible bugs that an atypical user would find in your code. Coding this way also hinders the refactoring process because classes are tightly coupled and introducing a small bug in your program is nearly impossible to find.

From now on I will attempt this form of developing. It will be different at first and I possibly won’t be AS productive at first, but once I get the hang of it I will be sure that my code is both clean and maintainable.

From the blog CS@worcester – My Progression as a Developer by xg2016 and used with permission of the author. All other rights reserved by the author.

Post From Week 3/7-3/11

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.

The Clean Coder – Chapter 4 and 5

I continue to enjoy this book a lot and glean valuable information pertinent to developing myself as a professional and continue to enhance myself and my career. Chapter 4 focuses on Coding and the goals of a programmer. A software developer’s code must first and foremost solve the problem at hand. Code should solve the correct problem, and a professional developer must often determine what the correct problem actually is by interacting with the customer and business analysts. Any new code developed must integrate seamlessly with the existing system, and must be readable by any other developers.

In Chapter 4, Martin also cautions the reader about 3 AM Code and Worry Code and advises them to take a step back instead. Writing software at 3 AM after staying up all night trying to solve a particularly perplexing problem is not going to produce quality code, nor is coding while personal issues are at the forefront of your brain. I often find it hard to pull myself away from a difficult task and basically just sit at my machine making no progress, only to think of am easy and elegant solution on my drive home as Martin mentions later in the chapter. Martin asserts that taking a step back and clearing your mind will often result in seeing the problem in a new way, and a solution will come to you, and I would have to agree.

Martin also voices his opinions on The Zone and listening to music. I do believe that sometimes certain types of music like video game soundtracks help enhance my concentration and also somewhat block out outside distraction. I know distractions happen and are a regular part of work, but it can be incredibly detrimental to progress with distractions often occupying more time than dedicated development. I don’t mind interruptions as being part of a team and working towards a common goal is important, but if it hinders my own tasks and goals then it is actually quite harmful.

I’ve never really had Writer’s Block when it comes to writing code, as I usually can just move on to a different task or go through, but I see how pairing can help alleviate the inability to progress. Martin also mentions the dangers of working overtime and how it is generally only helpful in some cases. I would have to agree that helping others is also important even if it can sometimes be frustrating if you need to focus on a particular task, one should know that they also  require help sometimes, and asking for help when you need it is okay.

When I first began developing software professionally, I had the view of debugging Martin initially described in which it was something that had to be done and was not really a part of coding. But in part due to reading this book and my growing desire to be more professional, I have changed my views and always spend the necessary time debugging. However, I find it difficult to subscribe to Test Driven Development in some cases even though I believe it would be extremely beneficial.

Chapter 5 is entirely about the benefits of Test Driven Development, and Martin’s initial suspicion but eventual embracing of the practice. I’m not sure if I’m jaded or believe that it is very difficult to introduce TDD practices into an existing project with multiple systems involved. With JavaScript talking to a SaaS platform that then speaks to a Java backend, the amount of unit and integration tests is enormous, and verifying correct testing behavior for all aspects of the system is very time consuming, but generally worth it. Regression and automated testing are invaluable when it comes to developer productivity and assurance of correct behavior. TDD enables a developer to freely refactor code while ensuring that existing functionality is not disrupted. TDD also significantly reduces defect rate by verifying that new code is working the way the developer intends.

Overall I am enjoying this book and finding it incredibly useful as a tool to make myself more of a professional.

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

Chapter 2 and 3

These chapter were very interesting to me and defiantly a good skill to learn before going in to the real work world.  The first thing that I got out of the chapter is that it is okay to say “NO”.  You just have to be conservative and actually not be able to do it.  This means that when you actually cannot have a task time done on time then it is okay to say no and be able to ask for a little more time.  In my opinion sometimes it is better to take a little bit more time to get quality work and instead of rushing and not having it working.  Chapter 3 was kind of the opposite of this chapter and was all about saying yes.  The chapter says that saying yes means that you say you can do it, you mean what you say, and that you can actually do it.  This means that when you say yes to a task or responsibility you are saying that u can definitely get it done and you are in charge of making sure that you are getting done.  Overall the chapter was really good at making sure that you are being professionally when giving a response for a task, make sure that when you say no that you actually mean it and you cant actually get it done and the same with the opposite is to make sure that when you say yes you can get it done for sure.

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

Clean Coder ch.5: TDD

The author is very much in favor of Test Driven Development, but while I am not opposed to it, I do not feel that it is always necessary. TDD is excellent for more difficult program projects, especially those with a lot of closely working parts, but when you have a program that is made up of many simple pieces, TDD seems to slow me down. I end up writing tests eventually, but when I do write the tests later on, I have a full view of what my program is doing, making it easier to write needed test cases. Starting by creating tests is a great idea, and I do use it from time to time, but it is just one style, and each style has its strong moments and its weak points. As a final note I will say that I should use this more than I do, and that sometimes I do need to slow down.

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

Clean Coder ch.5: TDD

The author is very much in favor of Test Driven Development, but while I am not opposed to it, I do not feel that it is always necessary. TDD is excellent for more difficult program projects, especially those with a lot of closely working parts, but when you have a program that is made up of many simple pieces, TDD seems to slow me down. I end up writing tests eventually, but when I do write the tests later on, I have a full view of what my program is doing, making it easier to write needed test cases. Starting by creating tests is a great idea, and I do use it from time to time, but it is just one style, and each style has its strong moments and its weak points. As a final note I will say that I should use this more than I do, and that sometimes I do need to slow down.

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

Clean Coder ch.4:Coding

This chapter was full of excellent tips and many hard truths. I would love to believe I work better by listening to music, but it is not the case. Recently, I have stopped listening to music while doing work and I get things done much faster. The writer of Clean Coder knows that it is usually distracting as well, and advises others not to multi task as it either leads to distraction or what he calls “entering the zone”. He makes the point that entering the zone is not a good thing because while you may get more done when you are extremely concentrated, you may make bad decisions that will later cause you to go over that code again to make changes. This is a valid point, but for me personally, I seem to always be in either one of two states: concentrated or distracted. If I am focusing on something, every thing else is a blur. If you talk to me in this state, I probably will not hear you. And if I stop and go do something else, it takes a bit for me to concentrate again.

Some of the other points he made was the distractions of worrying, interruptions, and writers block. These are all real life situations that get in the way of our thinking, and we need to find our own ways of combating these inhibitors. Worrying causes us to always be thinking of our situation than what we need to work on right now. Interruptions can cause us to snap at others for breaking our concentration. And writers block is the inevitable situation we find our selves in from time to time that stunts our productivity. His solution was pair programming, and while this is a good thing to keep in mind, we can’t always work with someone else. Sometimes we do not have access to another person for insights.

Lastly, he also goes through the debugging process in detail, explaining why debugging is so important. Debugging is not a waste of time or something that just has to be done, it is a part of programming and is just as costly as the program itself. Debugging is what tells you the quality of your code. Without it, you are basically taking a test without finding out how you did on it. Lastly, he mentions how time allotment and scheduling is important as well, and how bad pacing can cause late submissions. Being late is what we strive not to do, but when it does happen, we need to alert others as soon as we realize our blunder.

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