What did I learn this sprint?
With each passing sprint, our team is able to find better and easier methods to communicate and accomplish our tasks. Each of us has our specific responsibilities and we each make sure that our tasks are done. We also made great strides sharing our repositories using gitlab. We each were able to pull the latest AMPATH builds as well as having a teammates merge request accepted by the application owners.
Refactoring the Online Tracker
Our team was tasked with separating the online status marker with the logic that determines whether or not there is an active internet connection. We were to refactor the existing code to provide a clear distinction between the display and controller. Once completed, we packaged up the change into the proper merger request and sent it to AMPATH.
After some minor adjustments to make the request pass the tests, our update was accepted and our teammate, Jason Knowles, now has a contribution credit to the AMPATH application.
Dealing with Pouch DB
Installing and configuring Pouch DB proved to be a particularly difficult task. Our team discovered that some of the customizations made by the AMPATH team add a layer of difficulty to installing other third party modules.
After some setup, we were able to get Pouch DB up and running within the AMPATH application. We also provided a node with which to interact with the database instance. We could also create temporary records that existed in memory. When we tried to write these records to a permanent file, we ran into problems. There was errors regarding the CORS pattern that we had to use to connect to the AMPATH test server.
Having discovered that the CORS module could be disabled once a connection was made to the test server. Once we disabled this, the records that were giving us trouble we successfully creating permanent records.
From here, we decided to reach out to the AMPATH development team next sprint and show them some workflows to be created next sprint.
What did I do this sprint?
I completed tutorials for both Pouch DB and Encrypt JS for use with the upcoming sprint. We need to establish a strong understanding of how the modules work and the development tools they provide us.
I offered answers to some important questions my team had about the appropriate usage of subscribers, observables, and promised. We had extensive conversations about callback functions and the concept of a function as a primitive data type.
Each of these concepts requires a little bit different way of applying things we have already been taught. I provided insight and answers into their application in the context of Pouch DB specifically and asynchronous requests.
What Can We Do Better?
The next sprint, we will be focusing on furthering our momentum as we learn more about the intricacies contained within these modules. We must learn to better communicate among the groups within the class. We have gotten better as not overlapping work but there is plenty of room for improvement.
We can also leverage the tools given to us in a more productive manner. Trello, for example, has not proven to be the useful device that it has first seem to be. We should also be using the other items as well.