https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/c8faf74ca26ca4a71df0fb5fa09a428c0c473172
[fix: server persistence issue resolved] – The entrypoint that connected the server and the backend image terminated before the server could build itself.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/162e710813fe4efd59ee9dfdf6d8bd387eabd864
[Merge branch ‘API’ into ‘main’] – Packaged my work on the API (endpoints, openapi.yaml, javascript classes, and database methods) and combined it with the main branch.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/03ca867390a3541020e52b5bce95102002890fda
[chore: updated README.md] – Embedded hyperlink to reference repository and filled in some of the project details.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/ddbc5ae04b174ec3d2bcf981b888726345c6d410
[fix(data):”data folder rename to inventory-data”] – The .gitignore was set to not track any folder titled data, the inventory.js object was in a folder called ‘data’ and as such I changed the folder name.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/514777ff2ff6cd531bee0b480c3d946d7b6cba13
[Merge branch ‘inventory.js’ into ‘main’] – While the server would build correctly, the API was not pathing correctly and any calls would result in 500 errors, skipping the executing body of the endpoints and this was my fix.
Throughout this sprint our team as a whole was rather productive. We planned out some targets for the weeks and were constantly asking questions to the professor so that we understood the goalposts we could set for ourselves. I believe we learned a lot, I myself certainly learned a lot. For instance, in order for the frontend of our project ( https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based ) to use the backend I worked on we needed an image to be pulled from gitlab. The trick was that in order for gitlab to make the image of our backend it needed to pass the project’s pipeline, which we had not even begun to look at and turned out to be extremely labor-intensive. But we asked the professor when we had confusion which would generally set us back on the path and sometimes we just asked general questions on stuff we had not yet touched on so that we could tackle another piece of the project at a later date.
We were not always able to make it to meetings. At the beginning of this project we had made agreements to make it to all the class meetings and last sprint we added a Saturday call that begun at one. I know that I missed one of the Saturday meetings due to being sick but as a group I cannot recall a day where we all were in the call and that does sort of stick with me since at least once members of the group verbalized that they would be there and then not show up. In my opinion, it is crummy to be putting in the effort to have this meeting that everyone in the group agrees is the correct thing to do yet there are group members that are not participating just about every week.
I think a contract needs to be made, not a legally binding one mind you, that has input from every member of the team and is signed by every member of the team. To be clear, this is not something where it is forced upon each person to sign. If any one has an issue with a part that someone else offered then as a group we should come together and compromise on the issue so that everyone agrees to the provision. This is just a way I thought of to put a little more concrete understanding into the team dynamics.
As an individual I have not held up to my end of the agreement I made with the team. I said I would put forward updates to the group every week so that everyone understood my progress in my work and I utterly failed to follow through. I will simply have to keep this promise in mind for this next sprint.
Pattern : Use the Source
Summary : Seek out other people’s code and read it.
Reason for selection : Throughout this sprint I had Thea’s Pantry GuestInfo Backend open in my browser and I was constantly referring to it whenever I was confused about my codes errors.
How it would have changed me : In this case reading up on this pattern would not have changed my approach and in fact this is the reason I picked this pattern. I was already following through on this Apprenticeship pattern and reading it allowed me to put my methodology for this last sprint into words.
From the blog Coder's First Steps by amoulton2 and used with permission of the author. All other rights reserved by the author.