Monthly Archives: March 2017

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time
around the sprint seems to be getting more comfortable as far as us
working as a team and getting things done as well as discussing what
needs to be done and who will be doing what and the likes. It has
been a rather uneventful sprint in my opinion as we did some waiting
on the folks at ampath to figure out what they wanted us to do and
came up with 4 issues in the Jira board for us. That was actually
pretty cool to see an issues board and to see how it operates as I am
sure that when I get a job in the field I will be using something
similar. We had a roll of for who would get what issue because our
team and another wanted to work on the same issue. We lost and got
our second choice, NGPOC-185 in which there is a concern over logging
out when you are in the middle of filling out a form it doesn’t
save the data you had in the form and they would like a modal to pop
up asking if you would like to save or not. I have been going over
ampath code as well as documentation(Angular) to learn about where
the issue is and how to implement a fix.

I gained some more
knowledge this time writing the login and auth modules. It was a bit
of my own and a bit of looking at the code when I needed to, bu I
feel more comfortable with Angular, not like super but confident I
can actually do stuff with it now. I have also been going through a
book on Angular 2 by Pablo Deelman called “Learning Angular 2”
courtesy of ACM. It is good book so far and basically covers
everything needed for Angular including testing. It should help me
gain more experience with the language.

There really isn’t
much more I can offer, but next sprint looks like it will keep us
fairly busy as we should have the issue solved and implemented and
apparently there is a list of other issues for us to tackle now so
things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Week 5 Reflections

Well this time around the sprint seems to be getting more comfortable as far as us working as a team and getting things done as well as discussing what needs to be done and who will be doing what and the likes. It has been a rather uneventful sprint in my opinion as we did some waiting on the folks at ampath to figure out what they wanted us to do and came up with 4 issues in the Jira board for us. That was actually pretty cool to see an issues board and to see how it operates as I am sure that when I get a job in the field I will be using something similar. We had a roll of for who would get what issue because our team and another wanted to work on the same issue. We lost and got our second choice, NGPOC-185 in which there is a concern over logging out when you are in the middle of filling out a form it doesn’t save the data you had in the form and they would like a modal to pop up asking if you would like to save or not. I have been going over ampath code as well as documentation(Angular) to learn about where the issue is and how to implement a fix.
I gained some more knowledge this time writing the login and auth modules. It was a bit of my own and a bit of looking at the code when I needed to, bu I feel more comfortable with Angular, not like super but confident I can actually do stuff with it now. I have also been going through a book on Angular 2 by Pablo Deelman called “Learning Angular 2” courtesy of ACM. It is good book so far and basically covers everything needed for Angular including testing. It should help me gain more experience with the language.

There really isn’t much more I can offer, but next sprint looks like it will keep us fairly busy as we should have the issue solved and implemented and apparently there is a list of other issues for us to tackle now so things are starting to get rolling along. Until next time….

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

Sprint 3 Reflection

This sprint was the most productive so far. Each member of the team was given access to the AMPATH JIRA site. The AMPATH team uses JIRA to track issues and layout tasks than need to be completed. Now that we have access to the issue tracking system, a member of the AMPATH team picked a list of issues he though the class could handle. The issue we decided to tackle was not an issue with the code but a request by the users to move a button. The process of moving the button started off slow as we could not locate the button in question with in the system. This problem was further complicated by the fact that we could not load the forms on the site. After messaging our main contact at AMPATH we had an idea of what needed to be done but still were having issues locating the button. After some exploring we finally found the button. The button is to return to a form draft, this button is only visible if there is a form that has been open but not submitted. Our initial efforts to find the button were destine to be fruitless as we could not load any of the forms.
I believe the coming sprint will be the the first sprint where we can fully experience the Scrum process and see how the team works together. The past weeks have been good but with only smaller tasks it there was no sense of urgency. Now that we have an issue to work on team members will need to take responsibility of there individual part.

From the blog CS@WSU – :(){ :|: & };: by rmurphy12blog and used with permission of the author. All other rights reserved by the author.

Sprint 3: Reflections on Learning & Work Products

This sprint was the most successful yet.  I think we are all starting to really get the hang of things in our group and daily scrum meetings each week.  We are now at the point where we have been assigned issues from AMPATH and are diving head first into the openMRS code.  My big obstacle this week was trying to figure out why it was saying I had the wrong login credentials for the AMPATH standalone server.  I realized half way through the sprint that I was stuck on the issue for too long, so I decided to go to my teammates for help.  In a few days, one of my team members actually found the solution to the issue.  All I had to do was switch my web browser to google chrome and download a plugin I was missing.  The lesson I am going to take from this sprint is to not spend too much time getting stuck on something without asking for help.  It is always a good idea to try and figure out a problem by yourself but if it’s coming to the point where it is taking you a little too much time, you should always ask for help.  This semester is pretty short, so I don’t want to waste any time that I could be focusing on something else.  This next sprint I plan to get more done then I did this sprint.  I am not completely satisfied with the amount of work I accomplished this sprint and wish to improve.

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.

Sprint 4

This Sprint, we got everyone on board with AMPATH test2 server and checked out the code issue that was assigned on JIRA. It was interesting that we spent a huge amount of time trying to get standalone server to work and then it became useless as we transition to the test2 server.

We have an interesting issue on our JIRA issue in that we are unable to reproduce the error that was given to us. The JIRA issue was that a randomly typed location can be typed in and saved. When we tested with the test2 server, the location if randomly typed cannot be saved. I have commented on the JIRA ticket asking for clarification on this issue. Meanwhile, we are all just studying the code base for further understanding of the entire AMPATH system.

From the blog CS@Worcester – Site Title by nealw5 and used with permission of the author. All other rights reserved by the author.

Reflections (3/8/17) Week 5

This sprint has definitely been a busy one. After everyone got the programs downloaded and the server accessed, everyone was waiting for their invitation to the JIRA tracker for AMPath so we can all get ready to work on bugs. Before the bug tracking, we had an open conference online with developers of AMPath where developers were talking about different projects they are working on such as rewrite code to angular 3. It was after the conference that we start focusing on the bug tracking. I was one of the first ones to get an invite to the tracker so  I set up my account and showed off the tracker to my team. We did not know what bug we were going to work on but we were told that everyone will get to pick in the next class.

Eventually, after a coin flip and discussing among other groups, we decided to take the issue in the tracker known as AMRS-287, which was an issue that wasn’t really priority to address but would have been nice to take care off. The issue in detail was to find the “return to draft button” when navigating the forms and then move it to a more convenient place. Originally we thought it was an easy thing to do, but it was a bit more involving than we thought since we ran into some difficulty. First and foremost we had trouble finding the button. This took the longest portion of the sprint. We knew that we had to go to the locations where the forms were located to find the buttons but the links to the forms would not open for the life of us. We did not know what was happening, let alone we tried other servers as well to see if it worked and they did not.

Eventually I contacted Johnathan Dick through the tracker and he said to use the same test server we were using to find the button and edit the code. We tried again the week after, and then Kyle managed to find it after managing to access the forms. This was strange but the forms were accessed this time around. We debated where to put the button, and we decided to put the button near the task bar either above or below the vitals. We did not decide on a final place just yet but we will soon and hopefully take care of that button.

Other than the button issue, we have to address team behavior in regards to lateness so we are going through that as well, and that is to be continued.

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.

The Clean Coder Ch. 13 and Ch. 14

This week I read the final two chapters of Robert C. Martin’s The Clean Coder.  These chapters were not very long and only covered a couple topics.  In fact I only took away two points from chapter 13 on “Teams and Projects.”  These two topics were on the “Gelled Team” and “Velocity.”  A quick overview on Martin’s “Gelled Team” is a group of about twelve programmers, testers, analysts, and one project manager, who have worked long enough together to develop a symbiotic relationship.  I have worked closely with a few students during my time at WSU and we have certainly developed something close to what Martin described.  I know how these students think and work, and it aligns well with my process.  Martin describes “velocity” which my group and I have been experimenting with and adjusting as we figure out how much work we can accomplish over our sprints.

Chapter 14 was entitled “Apprenticeship, and Craftsmanship” which focused on the idea that school does not prepare programmers for the field.  To be honest I am concerned that I have not accrued enough knowledge to be an effective programmer in the field.  Martin suggests a system in which there are Masters, Journeymen, and Apprentices, where the more experienced teach the less experienced.  I like this idea, where for the first year, the Journeymen teach the Apprentices, and over time the Journeymen become Masters who orchestrate the entire process.  Martin also discusses the idea of Craftsmanship, which he calls “a mindset of values, disciplines, techniques, attitudes, and answers,” which are handed down from the experienced to the inexperienced.

Well that wraps up, The Clean Coder.  Stay tuned for more posts starting next week on a whole new text!

From the blog cs443 – TayNock's Blog by taynock and used with permission of the author. All other rights reserved by the author.

Learning Reflection – Sprint 3

I was studying the ngpoc-184 issue and I figured there are basically two modules that we need to work with: clinic-dashboard and main-dashboard. I also found a few questions in stack overflow useful in helping us develop the feature requested. We did not do anything else during this sprint.

I wish we could move faster as a team and take on more issues, but everyone else is still learning Angular 2 so we can’t move any faster.

From the blog CS448 – The blog about software by Sudarshan and used with permission of the author. All other rights reserved by the author.