Sprint 5

This sprint we have all been working on one issue together as a team.  Our biggest challenge so far was actually simply finding the file in the huge code base.  We looked everywhere for this one file and had no luck.  I decided to try a different tactic then to just search the full code base for keywords.  I looked at previous solved issues on GitHub for a similar problem.  I think that using GitHub as a resource was the best decision I made.  I was able to find the file within a half hour.  I will now use this method for finding files in the future.  A big obstacle we are currently stuck on is that the file is actually not in the openMRS src code on GitHub.  It would be such an easy fix to make a small change to the file, but it is part of npm and AMPATH has no access to it.  The next steps I am going to take is asking some of the other openMRS developers for some guidance on what exactly we should do.

From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.

Capstone: Sprint Reflection 5

This previous sprint was quite a successful sprint. We successfully had our code accepted into the Ampath project this previous sprint! It took us a while to get the understanding we required for the issue, but once we fully understood the issue it only took the team about a day to come up with a valid working solution. Once we as a team had decided to create a pull request, I went ahead and initiated this task. The biggest speed bump we hit for sure this sprint was getting the fix officially accepted and pulled into the project. The Ampath team had a specific set of guidelines they would have liked us to follow, we were not aware of these guidelines to begin with however. The first thing we needed to do was officially have the Ampath QA team checkout our fix and run it against their test systems. Then once that occurred once more developer was required to test the fix and check the quality of the code being applied to the fix. Once this was done our fix was accepted.

The second phase of Sprint was information gathering for the next issue we are working on. Towards the end of the sprint we received clarification on the issue and we have found that this may be a trickier issue then we initially thought. We are excited to get working on this issue this sprint, because we would like to see at least one more accepted change from out team before the semester’s end.

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

Retrospective Sprint 5

Splitting into teams proved to be a wise decision on our part. We are able to tackle three problems at once, and although my pair’s problem isn’t ready for a push yet, we have made much progress. My specific problem involves letting the user know if their contact information saved correctly upon clicking the save feature. We were able to locate the save feature in the code, and adding a basic browser alert window was pretty simple however we decided it did not fit well with the structure of the website. We are now attempting to recreate the small module that the contact information appears in, in order to have our save message display as well. Overall we believe it will fit much better with the flow and look of the site. We are heading into our final full sprint on top of finals and papers piling up, but we are determined to finish the bugs we have assigned to us.

From the blog CS@Worcester – Kyle Polewaczyk by kpolewaczyk and used with permission of the author. All other rights reserved by the author.

Sprint 5 Reflection

In Sprint 5 we were finally able to make meaningful code changes on our new issue (APTS-296). We basically focused the entire team on the issue because the semester is quickly coming to a close and we want to have a pull request accepted before our last sprint finishes. This issue took a while to figure out because the code we needed to modify was in the node_modules directory and we were only focusing on the src directory. Once we broadened our search to node modules we able to successfully modify the code and run it on the AMPATH test server. I think by focusing everyone on our issue it allowed us to make sure we were able to come up with a solution. Luckily during this sprint nobody has had server issues and we have been able to pull changes from upstream with no major problems. Looking at the next sprint our main focus will be to get a pull request submitted and accepted. To do this we will need to set up Travis CI on our team’s GitHub repository and squash all commits to one so that AMPATH accepts our changes. Overall we had a productive sprint and we will focus all of our effort on the pull request in our last sprint.

From the blog CS@Worcester – Software Development Blog by dcafferky and used with permission of the author. All other rights reserved by the author.

The Software Craftsmanship (Week 10)

This blog post will revolve around chapters 7 and 8

Chapter 7 talks about how beneficial technical practices are and ways to convince your peers to adopt the same practices. There were many repetitive things being stated in this chapter that I’ve already learned before. One of them is the idea of the “boy scout rule”, which is to always leave the campground cleaner than you find it.

Chapter 8 discusses on the steps to build a career and what motivates us. There was a story in this chapter about the author having a dream on becoming a software engineer. He had many obstacles in his way, lack of english, average skills, but that did not steer him away from his dream. He worked and worked to master his craft and 10 year later, what was a dream turned into a reality. He was hired as a software engineer in the United Kingdom. This just goes to show that if you want something badly, then you have to go and get it no matter how many obstacles there are in front of you.

 

From the blog CS@Worcester – My Blog by justcodeit94 and used with permission of the author. All other rights reserved by the author.

The Software Craftsmanship (Week 9)

This blog post will revolve around chapters 5 & 6

Chapter 5 was very interesting. It was about being professional in the software developer industry. Becoming a software professional entails being honest, knowing the can’s & cannot, ethics and having a code of conduct. There was a very interesting story about Sandro Mancuso who was a slave to a company that he had work for. In this chapter, he stated that his old company had him start the work day at 5am and end at 8pm. I find this to be outrageous. I don’t think anyone should be working for that long, because it will burn an individual out, and most of the time, the code that they are putting in isn’t the very best. I hope they paid him a lot of money for having him work more than 10 hours a day.

 

Chapter 6 goes on to talk about the qualities of a good software. The author lists out steps that a software developer should follow in order to create great code. If you do this from the gecko, then in the future, maintaining it would not be a challenge. Being a professional in the workforce is imperative and one should always stick to being one in order to become successful.

 

From the blog CS@Worcester – My Blog by justcodeit94 and used with permission of the author. All other rights reserved by the author.

Reflections on Learning and Work Products, Sprint 5

For Sprint 5, our team decided to split into two groups of three people that would each work on their own issue. During this time we also looked into the other issues that were available to us and what we would be comfortable doing. Sadly for a good chuck of this Sprint I was away, but, due to my teammates keeping me up to date on what was going on via Slack, I was able to do some work while volunteering. I found out that they had chosen to work on the issue labeled APTS-254. The description for the issue was stated to be “User are requesting when a patient switches to 2nd Line the Viral Load Pop-up reminder should not pop until the patient has used the 2nd Line Regimen for 6 months.”

After pulling new changes that were made to the code, I started to look into the code and see if I could recreate the issue. I was unable to figure out anything on my end, so, when our group next met up, we tried to recreate the issue. However, we were not able to find where this “2nd Line” was or how to get a “Viral Load Pop-up reminder”. After that class we decided to ask for more clarification on the issue and steps to re-create it. Near the end of our Sprint, we were told that this issue would be found in the ETL Rest Server. After forking and cloning the repository, I tried to get it to work to re-create the issue, but I ran into some issues while doing that. At the start of the next Sprint, we plan to see if our team can re-create this issue in class and then start looking at the Rest Server code to see if we can identify where the problem is.

From the blog CS WSU – Techni-Cat by clamberthutchinson and used with permission of the author. All other rights reserved by the author.

Sprint 5 Learning Reflection Blog (4/12/17)

I can’t believe this is our last sprint! It went by so fast; it feels as though we are just starting. Overall it was definitely a good learning experience being able to collaborate with a real organization. Our group had a good conversation with our professor about this whole sprint experience with the AMPATH group and it kind of prepares us for what it would be like working for a company in the real world as a full-time job. Over the duration of 2 months we only were able to resolve one issue. By face-value it might sound bad, but we spent the majority of the time trying to understand the language of Angular2 and the framework of how everything operated. If you think about it, my experience with this is pretty similar to what it will be like when working for your first company; most of the time will be getting used to the coding language and the framework. Prepare to be doing that most of the time before you even begin coding anything!

From the blog CS@Worcester – Tan Trieu's Blog by tanminhtrieu and used with permission of the author. All other rights reserved by the author.

The Software Craftsman Chapter 5 & 6

Chapter 5:

This chapter talks about the fact that a good developer does not consist of a mindless worker that does whatever the client asks of him. It tells us that we are in charge of our projects and only we know what is really good for our clients over what they want. It is our job to say no when needed and figure out what the solution to their problem really is and to advise them the right way instead of just doing whatever they ask. We do what we can to make sure everything they want is in their own best interest. They will never understand how you would go about your work so make choices based on your own well being and make sure to give them options and say no if ever needed.

Chapter 6:

This chapter goes into the details of the quality of code. You can’t make quality code that will last a long time if there is no quality in it. It will not last, and eventually it will be worthless. So don’t skip steps and make sure you take the long and hard road rather than the short one to a quicker fix. Many people fall problem to this because they are working on deadlines and need to finish in time which makes them take short cuts. Good softwares can change and adapt their ways quickly, that is how you know they are quality. Also unit tests are important and should always be used. No excuses. Time is in your hands, you always have it. It is just your choice of what you decide to do with it.

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

The Software Craftsman Chapter 3 & 4

Chapter 3:

We talk about what software craftsman is certainly not; test driven development, clean code, clarifications, or specific technologies. Software Craftsman is a metaphor for software development. It is a long journey of mastery, its core being professionalism. Everyone needs to contentiously change and adapt to the new technologies and soft wares to stay on top of their craft. It is their job as a software craftsman to stay up to date with the new and innovative techniques that replace the old ones. I agree with this because it teaches us not only to respond to change but to also add as much value as we can.

Chapter 4:

In this chapter we learn about our careers, and who is in charge of them. We are in charge of them, only we can strive to be better. We should never blame others for our failures and continue to strive to be better even if something or someone is actually holding us back. We should always be determined and make sure that there is passion in what we’re doing. We should try to track our progress and read books and blogs to help us to stay sharp.

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