During the second Sprint of this semester, me and my partner Hiercine worked on modifying all of the endpoints within the guestinfosystem backend to accept access tokens that will let the system know if the request comes from someone who is authorized to make that request. In other words, only admins/staff can delete guest information and normal guests cannot.
We had a lot more issues during this Sprint than we did in the previous Sprint. One of the major issues was how this Sprint was handled. We weren’t able to start our work until after one of the other groups finished determining how the tokens would be handled, as they were the ones creating the roles and assigning the tokens. By that point, we were almost halfway through our Sprint. Once they were able to determine how to use the tokens and we communicated with them, we came up with a draft for how to get the endpoints to accept the tokens and sent it to them. However, it turns out that they were using the tokens in a completely different way than we and the professor thought. On top of that, communication on both ends took multiple days just for a simple conversation. We didn’t come up with a solution to this issue during this Sprint, but we are going to continue to work on it and talk to the professor about it during the third and final Sprint.
Another thing we worked on during this Sprint was fixing some of the issues we had with the work from our first Sprint. It turns out that the format we used for the first visit date in the backend is different from the format that they are using in the frontend, so we had to match those formats in order or get them to work and communicate with each other properly.
While we did have a lot of issues during this Sprint, I think that we did a great job working together as a team. Me and Hiercine worked together on our issue all the time, even communicating outside of class in order to talk about potential solutions. On top of that, the rest of the group did a great job communicating with each other whenever needed. At the beginning of each class, we would check how everyone is doing and see if they needed help. Similarly, whenever helped was needed, we didn’t hesitate and asked each other right away. I don’t think we have much to improve upon as a team, however I would like to improve as an individual by doing more research on my own time instead of just in class.
A pattern from the Apprenticeship Patterns book that is relevant to my experience during this Spring is the “Use the Source” pattern. This pattern emphasizes the importance of digging into the actual source code when you’re trying to understand how something works instead of relying on secondhand documentation, assumptions, or waiting for explanations. I selected this patterns because of how Hiercine and I kept having to communicate with another group about how the tokens worked and had a couple misunderstandings, when we could have just looked at the code that was created. The “Use the Source” pattern encourages this behavior, allowing you to understand it yourself.
I think that depending on another group in order to be able to complete our task was the major issue we had during this Sprint. Instead of having us work on the issues at the same time, we should wait until the other group is completely finished.
We haven’t committed or merged anything yet, here is an image showing the draft we have so far checking the role in each endpoint as well as the link to the current issue we are working on.
The image shows the draft of the code added in the comments:

From the blog CS@Worcester – One pixel at a time by gizmo10203 and used with permission of the author. All other rights reserved by the author.