Category Archives: Sprint-3

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint #3 Retrospective

 Hello

I cannot believe how quickly this year has come to a close. It seems like just yesterday I was struggling comprehending what I was doing in this course, but now I have gotten to the point where I feel like I have a grasp on how things are actually going. In terms of what got done, I implemented Rabbit at long last, and it only took me 3 sprints to get here! Along with that I made sure the messages we were sending matched the specifications posted on discord, and I made sure that the messages were only being sent if the requests themselves were valid (i.e. weight isn’t null, and it won’t take more than the inventory has). I think I really came into my own near the end of my time in this class,  I did a good job speaking to my group more often, I put out a number of good commits, and overall I had a better grasp on what was actually going on, which I certainly couldn’t say at the start. Though if I had to pinpoint something that didn’t work very well, I definitely think it was my communication with my group about what all of my work actually does. I get consistently asked what certain ports are being used for, and near the end of the sprint we ran into a snag relating to a library I was using. If I had explained what everything was more thoroughly, it could have prevented some headaches in my opinion. Our team continues to work quite well together, we communicate pretty openly at meetings, and I am not afraid to ask questions like I was before. I think near the end of the sprint we kind of lost focus a bit, and we, myself included, started slacking off on things once the majority of the sprint’s work had been done. We might have been able to come up with some other issues than the ones we have posted on Gitlab, but perhaps we wouldn’t have, who can really say for sure, our stuff is basically already done from my understanding. As for me, I am trying not to slack on any of the work required for this class in the last weeks of the semester. While the last presentation is a good week or so away, I am trying to make myself as available as possible, and I am trying to keep on top of everything so that the presentation isn’t rushed. 

For the design pattern I’ve chosen for this post, I went with something that I feel really encapsulates all of the work I’ve done over the course of the semester, and that is Sustainable Motivations. The pattern states that a software craftsman should hone their skills to cope with ever changing specifications and demands from customers. It recommends trying to remain motivated by writing things down that motivate you about your work, and trying to keep in mind that not every day programming will be perfect. Throughout the course of the semester I have had a kind of moving target problem with the scope of my work. At the beginning, the issue I was assigned requested I use RabbitMQ to send messages on inventory actions, but it did not mention the fact that RabbitMQ wasn’t implemented in the Inventory Backend at all. So suddenly, the scope of my work had changed dramatically, and I spent most of the first sprint stressing that I wasn’t doing as much as I should while I got RabbitMQ running. Later on, things like queue creation and library conflicts became a problem, and it seemed like the further I got in, the farther away completion of my goal was. I think if I had read this pattern at the start of the semester, or even at the start of sprint 3, I would have taken some time to actualize that I was never going to have a static goal with this kind of work, and perhaps I would have cut myself a little slack in that regard. 

Overall I’ve enjoyed this class quite a bit, and my time in college in general, since I am graduating. I’ve learned a lot from this course, and gained a lot of experience that I will doubtlessly use in industry. So, all that remains now is for me to coast through the finish line, and see where my career takes me from there.

Thanks for reading my blog! Who knows when or if I’ll post again, but it’s been interesting writing about all the work I’ve been doing for classes in a public facing way. I might even try this whole thing again sometime, who knows! :p

 

Merge Requests:

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/69

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/68

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-weight-based/inventorybackend/-/merge_requests/66

From the blog Camille's Cluttered Closet by Camille and used with permission of the author. All other rights reserved by the author.

Sprint 3 Retrospective

In this post, I’ll be reflecting on our third and final sprint towards developing and implementing an Identity and Access Management system for Thea’s Pantry. Coming out of Sprint 2, we had an almost-fully-functional proof of concept which integrated a mock frontend capable of calling out to Keycloak to require authentication, getting an access token, and passing that token to the backend for authentication and validation. Our goal for sprint 3 was to fully implement production microservices for Keycloak, the IAMBackend, and the IAMFrontend. These goals may not have been explicitly defined like that at the beginning of the sprint, but that ended up being our objective. We also wanted to have finalized documentation that explains our implementation and design choices.

Some of my personal work towards that goal was as follows:

GitLab

  • Documenting our low-level issues in GitLab and assigning them accordingly. I put additional focus/effort this sprint into properly linking related issues, blockers, and tracking various key information in comments, as opposed to just using issues as a task list. Epic

  • Document and ticket/issue any outstanding work that is necessary but out of the time constraints of this sprint / the semester. Approaching the end of the semester, there is still some necessary work to fully implement our microservices, but there is not enough time to complete it all. I have gone through and added any issues I can think of.

Backend

  • Fully implement an IAMBackend that mirrors the structure of the GuestInfoBackend. It is not yet merged, as it is not yet a fully functional MVP. That branch is here. This has included but was not limited to work such as:

    • Refactoring comments and text to apply to an IAMBackend instead of GuestInfoBackend

    • Removing files and code that does not apply to IAMBackend, such as messageBroker.js

    • Modifying backend endpoint code to finalize it

    • Updating dependencies

    • Ensuring the GitLab build processes function as expected

  • I will be tying up some loose ends and hopefully merging IAMBackend before “finishing” the semester.

Frontend

  • Fully implement an IAMFrontend that mirrors the structure of the GuestInfoFrontend. It is not yet merged, as it is not yet a fully functional MVP. That branch is here. This has included but was not limited to work such as:

    • Refactoring comments and text to apply to an IAMFrontend instead of GuestInfoFrontend

    • Updating dependencies

    • Ensuring the GitLab build processes function as expected

    • Adding and reconfiguring bin scripts as necessary

    • Doing frontend Vue work to actually create a redirect page

  • I will be tying up some loose ends and hopefully merging IAMFrontend before “finishing” the semester.

PantryKeycloak

Just providing a link to the repository because I am the only one that has touched it, all work in there was done by me. PantryKeycloak

  • Fully configure and implement a production Keycloak repository

  • Add all custom settings for the TheasPantry Realm

  • Create an entrypoint script that automatically exports and saves all changes to the realm

Documentation

Documentation Repository

  • Finalize and write a lot of documentation

I feel like this sprint was a rough one across the board. I could definitely tell people were on the home stretch and sliding towards the end of the semester. I think people did good work, and our class meetings worked well for us; we always came to agreements and had purpose. I feel like we were working very slowly though, and at times, I felt like I was taking the bulk of the issues on myself. I think I could work on that as an individual, and understand that it is not necessarily my job to make sure every single thing gets done. I am very mission-oriented, so I naturally do that, despite the cost to myself. I feel like as a team, we could have paid more attention to each other and what people’s workloads looked like. That might have allowed us to work better together and be more mindful of our own deadlines and how we can help each other.

The pattern I have chosen for this sprint is Dig Deeper. This pattern describes learning things at a level where you truly understand why they are the way they are, how they work, and how to use them. I think it is relevant because the more I tried to learn how the different services and Docker interact, the better I was able to understand and implement solutions. If I had read this prior, I may have focused more on understanding before trying to implement, as opposed to while.

From the blog Mr. Lancer 987's Blog by Mr. Lancer 987 and used with permission of the author. All other rights reserved by the author.

Sprint 3 Retrospective

In this post, I’ll be reflecting on our third and final sprint towards developing and implementing an Identity and Access Management system for Thea’s Pantry. Coming out of Sprint 2, we had an almost-fully-functional proof of concept which integrated a mock frontend capable of calling out to Keycloak to require authentication, getting an access token, and passing that token to the backend for authentication and validation. Our goal for sprint 3 was to fully implement production microservices for Keycloak, the IAMBackend, and the IAMFrontend. These goals may not have been explicitly defined like that at the beginning of the sprint, but that ended up being our objective. We also wanted to have finalized documentation that explains our implementation and design choices.

Some of my personal work towards that goal was as follows:

GitLab

  • Documenting our low-level issues in GitLab and assigning them accordingly. I put additional focus/effort this sprint into properly linking related issues, blockers, and tracking various key information in comments, as opposed to just using issues as a task list. Epic

  • Document and ticket/issue any outstanding work that is necessary but out of the time constraints of this sprint / the semester. Approaching the end of the semester, there is still some necessary work to fully implement our microservices, but there is not enough time to complete it all. I have gone through and added any issues I can think of.

Backend

  • Fully implement an IAMBackend that mirrors the structure of the GuestInfoBackend. It is not yet merged, as it is not yet a fully functional MVP. That branch is here. This has included but was not limited to work such as:

    • Refactoring comments and text to apply to an IAMBackend instead of GuestInfoBackend

    • Removing files and code that does not apply to IAMBackend, such as messageBroker.js

    • Modifying backend endpoint code to finalize it

    • Updating dependencies

    • Ensuring the GitLab build processes function as expected

  • I will be tying up some loose ends and hopefully merging IAMBackend before “finishing” the semester.

Frontend

  • Fully implement an IAMFrontend that mirrors the structure of the GuestInfoFrontend. It is not yet merged, as it is not yet a fully functional MVP. That branch is here. This has included but was not limited to work such as:

    • Refactoring comments and text to apply to an IAMFrontend instead of GuestInfoFrontend

    • Updating dependencies

    • Ensuring the GitLab build processes function as expected

    • Adding and reconfiguring bin scripts as necessary

    • Doing frontend Vue work to actually create a redirect page

  • I will be tying up some loose ends and hopefully merging IAMFrontend before “finishing” the semester.

PantryKeycloak

Just providing a link to the repository because I am the only one that has touched it, all work in there was done by me. PantryKeycloak

  • Fully configure and implement a production Keycloak repository

  • Add all custom settings for the TheasPantry Realm

  • Create an entrypoint script that automatically exports and saves all changes to the realm

Documentation

Documentation Repository

  • Finalize and write a lot of documentation

I feel like this sprint was a rough one across the board. I could definitely tell people were on the home stretch and sliding towards the end of the semester. I think people did good work, and our class meetings worked well for us; we always came to agreements and had purpose. I feel like we were working very slowly though, and at times, I felt like I was taking the bulk of the issues on myself. I think I could work on that as an individual, and understand that it is not necessarily my job to make sure every single thing gets done. I am very mission-oriented, so I naturally do that, despite the cost to myself. I feel like as a team, we could have paid more attention to each other and what people’s workloads looked like. That might have allowed us to work better together and be more mindful of our own deadlines and how we can help each other.

The pattern I have chosen for this sprint is Dig Deeper. This pattern describes learning things at a level where you truly understand why they are the way they are, how they work, and how to use them. I think it is relevant because the more I tried to learn how the different services and Docker interact, the better I was able to understand and implement solutions. If I had read this prior, I may have focused more on understanding before trying to implement, as opposed to while.

From the blog Mr. Lancer 987's Blog by Mr. Lancer 987 and used with permission of the author. All other rights reserved by the author.

Sprint 3 Retrospective

In this post, I’ll be reflecting on our third and final sprint towards developing and implementing an Identity and Access Management system for Thea’s Pantry. Coming out of Sprint 2, we had an almost-fully-functional proof of concept which integrated a mock frontend capable of calling out to Keycloak to require authentication, getting an access token, and passing that token to the backend for authentication and validation. Our goal for sprint 3 was to fully implement production microservices for Keycloak, the IAMBackend, and the IAMFrontend. These goals may not have been explicitly defined like that at the beginning of the sprint, but that ended up being our objective. We also wanted to have finalized documentation that explains our implementation and design choices.

Some of my personal work towards that goal was as follows:

GitLab

  • Documenting our low-level issues in GitLab and assigning them accordingly. I put additional focus/effort this sprint into properly linking related issues, blockers, and tracking various key information in comments, as opposed to just using issues as a task list. Epic

  • Document and ticket/issue any outstanding work that is necessary but out of the time constraints of this sprint / the semester. Approaching the end of the semester, there is still some necessary work to fully implement our microservices, but there is not enough time to complete it all. I have gone through and added any issues I can think of.

Backend

  • Fully implement an IAMBackend that mirrors the structure of the GuestInfoBackend. It is not yet merged, as it is not yet a fully functional MVP. That branch is here. This has included but was not limited to work such as:

    • Refactoring comments and text to apply to an IAMBackend instead of GuestInfoBackend

    • Removing files and code that does not apply to IAMBackend, such as messageBroker.js

    • Modifying backend endpoint code to finalize it

    • Updating dependencies

    • Ensuring the GitLab build processes function as expected

  • I will be tying up some loose ends and hopefully merging IAMBackend before “finishing” the semester.

Frontend

  • Fully implement an IAMFrontend that mirrors the structure of the GuestInfoFrontend. It is not yet merged, as it is not yet a fully functional MVP. That branch is here. This has included but was not limited to work such as:

    • Refactoring comments and text to apply to an IAMFrontend instead of GuestInfoFrontend

    • Updating dependencies

    • Ensuring the GitLab build processes function as expected

    • Adding and reconfiguring bin scripts as necessary

    • Doing frontend Vue work to actually create a redirect page

  • I will be tying up some loose ends and hopefully merging IAMFrontend before “finishing” the semester.

PantryKeycloak

Just providing a link to the repository because I am the only one that has touched it, all work in there was done by me. PantryKeycloak

  • Fully configure and implement a production Keycloak repository

  • Add all custom settings for the TheasPantry Realm

  • Create an entrypoint script that automatically exports and saves all changes to the realm

Documentation

Documentation Repository

  • Finalize and write a lot of documentation

I feel like this sprint was a rough one across the board. I could definitely tell people were on the home stretch and sliding towards the end of the semester. I think people did good work, and our class meetings worked well for us; we always came to agreements and had purpose. I feel like we were working very slowly though, and at times, I felt like I was taking the bulk of the issues on myself. I think I could work on that as an individual, and understand that it is not necessarily my job to make sure every single thing gets done. I am very mission-oriented, so I naturally do that, despite the cost to myself. I feel like as a team, we could have paid more attention to each other and what people’s workloads looked like. That might have allowed us to work better together and be more mindful of our own deadlines and how we can help each other.

The pattern I have chosen for this sprint is Dig Deeper. This pattern describes learning things at a level where you truly understand why they are the way they are, how they work, and how to use them. I think it is relevant because the more I tried to learn how the different services and Docker interact, the better I was able to understand and implement solutions. If I had read this prior, I may have focused more on understanding before trying to implement, as opposed to while.

From the blog Mr. Lancer 987's Blog by Mr. Lancer 987 and used with permission of the author. All other rights reserved by the author.