https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/3ae85c192e180983dcf961f20dcf16f085ddab26 :
[Merge branch ‘database’ into ‘main’] – This was a review by me of Marlon’s work which was focused on getting the pipeline on the backend up and running.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/202fc47311dc73df775d7f03b9994fcedb25eb46 :
[Merge branch ’15-yamlint-error-fix’ into ‘main’] – This branch had some tweaks to the pipeline as well as changes to the yaml files so that they were properly formatted for the pipeline.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/8cd54420550699a154d7e7c1d5fb662990d80a14 :
[Merge branch ‘fix-entrypoint’ into ‘main’] – This branch modified the endpoint files, the index.js entrypoint, and the inventory object, adding a new UPC code check, changing the default inDatabase check to use the name of a category, as well as some other functionality.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/backend/-/commit/24b16f138e0fcb22c04dcc99f73973a64bb1cd6d :
[Merge branch ‘opanapi’ into ‘main’] – This branch modified the openapi.yaml file link so that the server could read in the schema for the API and added a rabbitMQ message send on createCategory.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/commit/77f74b81324ad09e69f1815c14e95cc3698dcf32 :
[Merge branch ’12-connect-frontend-to-category-based-backend’ into ‘main’] – Says it in the title, I modified the docker-compose.yaml in the frontend to pull the image made through the backend pipeline so the frontend had a working backend.
Our communication as a team went really well this sprint. We had quite a bit more of back and forth due to the pipeline getting finished and being deployed to the frontend and also the backend image being called by the frontend. There were meeting on the weekends set up for these tasks and we were there and got the job done. I learned this sprint not to just trust the linters blindly, I spent quite a long time researching just to find out my issue was an improperly typed http header ( http:/localhost vs http://localhost ). Also learned that while the linting might fail, in our case due to the commit-message lint applying to all the branch commits and not just the last merge commits, the pipeline can still be set to continue to the testing part. This would allow an image to be built if the test passed even if the lint did not, which was contrary to how I understood the linter to work.
Throughout this sprint we had our roadblocks, but we would immediately ask the Professor whenever we needed his knowledge and expertise, but not so much that we hampered our own learning.
We did not end up implementing that “contract” idea I had and there was still some people missing from the meetings but I think this sprint those who were not at the meeting still got done the work that was expected of them. Again, we got the project done, the documentation is done, and the final presentation came out pretty well in my opinion. Is there room for improvement as a team ? Yes of course. But are those improvements able to be applied to the team ? No, the class has reached its end.
I could not access the Apprenticeship Patterns book through the host service, it has put up some paywall and I honestly do not want to make a brand new email and then a brand new account for the purpose of getting to look at this online book for 5 minutes. Instead I will say this, my experience this sprint was very different to the two sprints before. This was a “closer” sprint and the documentation step was more rigorous than I thought it would be. The stress of the “last pushes” of code was felt this time around. I have this somber feeling, I am done and did good work. Especially considering our group started with empty repositories, we did pretty damn good. But looking back I have that nagging thought, “I could have done more. I could have done this here and that there.” But as my Software QA professor said, “Good enough is good enough.”
From the blog Coder's First Steps by amoulton2 and used with permission of the author. All other rights reserved by the author.