From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

It took couple of days to trace down our new issue ‘APTS-296’. We all, as a team, had difficulty of tracing through the code. The main hindrance was the huge code base of the OpenMRS project.

We finally were able to fix the issue, and ran it successfully on the AMPATH test server 2. But the thing we are currently getting suck in order to push our changes is the module we modified is not a part of ng2-amrs src code. It seems to be using a 3rd party npm-plugin which is located under ‘node_modules’ outside of the src code folder.

We must ask AMPATH developers if we can edit the npm modules, if yes, then how.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

To be honest, we didn’t had significant progress during this sprint. One of the reason was that we had a spring break during this cycle, and the other one is, we waited long enough to the get clarification on our issue. Regarding our NGPOC-183 issue, we tried to reach out developers on JIRA as well as on Slack we but didn’t got any reply.

Therefore, we ended up assigning new issue named APTS-296. The issue is “Add 24 and 36 Weeks Under Week Control in Return Visit Forms”. As of now, we as a team, got a strong understanding of this issue and know what need to be fixed. Hopefully this one shouldn’t take long.

We are in progress towards making our first change.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.

The very first chapter titled “Software development in twenty-first century” discusses about what seniority really means and also the new reality faced by developers in the twenty-first century. Seniority is transient and relative, there is no such thing as a senior or junior developer.

Mancuso argues seniority is not just about composing code or being exceptionally acquainted with a dialect or system. Developers need to know how to address clients, automate tests and deployment, and settle on mechanical decisions that may influence the whole business.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.