Getting started with our first sprint, we were tasked with a few familiar tasks which included:

– Creating a GitHub repo for our team so that we could fork the AMPATH/ng2-amrs repositories
– Cloning the repos onto our local computers so we could edit/build the code
– And lastly set up our development environment to be ready so that when we have the back-end server up and running we could start immediately.

The first two tasks were pretty straight forward but when it came to setting up our environment we had many difficulties.
– The first of many difficulties was getting an error that stated we were missing some style.css packages. Since half of our team got this error we dedicated a large part of our time to figuring out what was wrong. James figured out that we had to install the missing packages, specifically ng2-ion-range-slider which got rid of this error. Starting npm was not an issue after this case.
– The second main issue we had to learn to work through were missing environments which I and Gulshan had. I found that since we never ran npm start, we wouldn’t have the environment. This fix took quite some time to figure out also but now most of us are on the same page; waiting for the back-end server to get set up.

There were many steps we tried that failed, some of which ate up a chunk of our time working as a team. We tried deleting and recloning the repos which did not work. We tried installing npm numerous times over and over but the result was the same. I believe most of our successes came from trial and error. We constantly tried updating all of our working environments, researched on stackoverflow, and worked collectively as a team helping one another to figure out our problems. Throughout the week whenever one of us made progress towards ridding one error we would post in our 404 slack channel for others to see; keeping constant communication.

If I were to instruct another individual who wishes to start working on this project I would be sure to have them follow a series of steps as well as solutions to errors that they might encounter. Before beginning anything I would suggest updating all versions of node and npm to the latest. From there, the first command to try and run is to be npm start in the working directory. If there are no errors then localhost:3000 should be all set, else if there are missing packages I suggest installing the ion package that was missing for most of us. We did not encounter any other sort of errors so I don’t know what else could go wrong.

Onto Sprint-2!


Author: iharrynguyen

Hello friends, my name is Harry Nguyen. I am a novice programmer and current student at Worcester State university anticipating graduation this upcoming May 2019. Feel free to follow me on my life-long journey as I continue to learn the ins and outs in the field of computer science.