Category Archives: CS448

Sprint #2 Retrospective

Hello!

It’s that time of the month again, we’ve just finished up sprint number 2, and now I’ve got to write about how it went! 

I think this sprint was considerably more productive than the last one (even if I still couldn’t get my assigned issue done). I managed to parse out how I am going to make timestamps for the rabbitMQ messages, and I did a significant amount of testing with some files, to the point where I basically had everything working by the end of sprint 2. It would have been implemented were it not for the fact that I ran into some last minute errors that I couldn’t get fixed in time. Like the last post I made, the merge request will be available at the bottom of the post.

I think I did a much better job at communicating with my group this time around. I think I was a little shy before, plus overwhelmed at having to learn a new skill and be a productive member of a group. Now though, I’ve been pretty consistently talking to my group about what I’m working on, and I’ve been asking questions on things that trip me up, which I would consider a wild improvement over last time.

 In terms of things that didn’t go so well, I could do with some better time management skills. If I had planned out my work a bit better, I probably would have had ample time to fix the errors I was getting, and I might even have been able to implement everything I had been working on. I’m not going to fret about that though, I just have to keep that in mind and make sure I give this sprint all the time it needs from me to get everything done. 

As with myself, our group has been doing a lot more communicating lately. Most of it has been really good, but a good chunk of it has not been very on topic. I’m not about to be some kind of narc that wants every minute of every day be spent working, that sounds utterly miserable, but I would like more of our discussions being related to what we are working on.

After looking in the book, I think the apprenticeship pattern that relates the most to this sprint was “Expose Your Ignorance”. The pattern states that the best way to fill gaps in my knowledge is to reveal them to my group, so that I might be more encouraged to find what I am missing. I’ve been the one working on rabbitMQ for two sprints now, and as such, I think it is easy to assume that I know every aspect of what it going on, but the longer I work on this project, the more small problems seem to come out of the woodwork. Oh sure, we have the code needed to send messages, but there is no queue for them to go into, so what is the point, etc. So, had I read this pattern at the start of the sprint, I think it would have been more productive to know what kind of stuff I was missing, so I can avoid any unexpected problems. I would have laid out the plan for the sprint, done some research on everything I was doing if I wasn’t 100% solid on it, and had some better fundamental knowledge going into that sprint than what I had. 

As usual, I will try to keep the things I learned in mind, but I will continue working on my issue, knowing that I do not have all the knowledge I need, and being willing to ask for help in finding it.

 

 

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

 

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

Sprint #2 Retrospective

Hello!

It’s that time of the month again, we’ve just finished up sprint number 2, and now I’ve got to write about how it went! 

I think this sprint was considerably more productive than the last one (even if I still couldn’t get my assigned issue done). I managed to parse out how I am going to make timestamps for the rabbitMQ messages, and I did a significant amount of testing with some files, to the point where I basically had everything working by the end of sprint 2. It would have been implemented were it not for the fact that I ran into some last minute errors that I couldn’t get fixed in time. Like the last post I made, the merge request will be available at the bottom of the post.

I think I did a much better job at communicating with my group this time around. I think I was a little shy before, plus overwhelmed at having to learn a new skill and be a productive member of a group. Now though, I’ve been pretty consistently talking to my group about what I’m working on, and I’ve been asking questions on things that trip me up, which I would consider a wild improvement over last time.

 In terms of things that didn’t go so well, I could do with some better time management skills. If I had planned out my work a bit better, I probably would have had ample time to fix the errors I was getting, and I might even have been able to implement everything I had been working on. I’m not going to fret about that though, I just have to keep that in mind and make sure I give this sprint all the time it needs from me to get everything done. 

As with myself, our group has been doing a lot more communicating lately. Most of it has been really good, but a good chunk of it has not been very on topic. I’m not about to be some kind of narc that wants every minute of every day be spent working, that sounds utterly miserable, but I would like more of our discussions being related to what we are working on.

After looking in the book, I think the apprenticeship pattern that relates the most to this sprint was “Expose Your Ignorance”. The pattern states that the best way to fill gaps in my knowledge is to reveal them to my group, so that I might be more encouraged to find what I am missing. I’ve been the one working on rabbitMQ for two sprints now, and as such, I think it is easy to assume that I know every aspect of what it going on, but the longer I work on this project, the more small problems seem to come out of the woodwork. Oh sure, we have the code needed to send messages, but there is no queue for them to go into, so what is the point, etc. So, had I read this pattern at the start of the sprint, I think it would have been more productive to know what kind of stuff I was missing, so I can avoid any unexpected problems. I would have laid out the plan for the sprint, done some research on everything I was doing if I wasn’t 100% solid on it, and had some better fundamental knowledge going into that sprint than what I had. 

As usual, I will try to keep the things I learned in mind, but I will continue working on my issue, knowing that I do not have all the knowledge I need, and being willing to ask for help in finding it.

 

 

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

 

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

Sprint #2 Retrospective

Hello!

It’s that time of the month again, we’ve just finished up sprint number 2, and now I’ve got to write about how it went! 

I think this sprint was considerably more productive than the last one (even if I still couldn’t get my assigned issue done). I managed to parse out how I am going to make timestamps for the rabbitMQ messages, and I did a significant amount of testing with some files, to the point where I basically had everything working by the end of sprint 2. It would have been implemented were it not for the fact that I ran into some last minute errors that I couldn’t get fixed in time. Like the last post I made, the merge request will be available at the bottom of the post.

I think I did a much better job at communicating with my group this time around. I think I was a little shy before, plus overwhelmed at having to learn a new skill and be a productive member of a group. Now though, I’ve been pretty consistently talking to my group about what I’m working on, and I’ve been asking questions on things that trip me up, which I would consider a wild improvement over last time.

 In terms of things that didn’t go so well, I could do with some better time management skills. If I had planned out my work a bit better, I probably would have had ample time to fix the errors I was getting, and I might even have been able to implement everything I had been working on. I’m not going to fret about that though, I just have to keep that in mind and make sure I give this sprint all the time it needs from me to get everything done. 

As with myself, our group has been doing a lot more communicating lately. Most of it has been really good, but a good chunk of it has not been very on topic. I’m not about to be some kind of narc that wants every minute of every day be spent working, that sounds utterly miserable, but I would like more of our discussions being related to what we are working on.

After looking in the book, I think the apprenticeship pattern that relates the most to this sprint was “Expose Your Ignorance”. The pattern states that the best way to fill gaps in my knowledge is to reveal them to my group, so that I might be more encouraged to find what I am missing. I’ve been the one working on rabbitMQ for two sprints now, and as such, I think it is easy to assume that I know every aspect of what it going on, but the longer I work on this project, the more small problems seem to come out of the woodwork. Oh sure, we have the code needed to send messages, but there is no queue for them to go into, so what is the point, etc. So, had I read this pattern at the start of the sprint, I think it would have been more productive to know what kind of stuff I was missing, so I can avoid any unexpected problems. I would have laid out the plan for the sprint, done some research on everything I was doing if I wasn’t 100% solid on it, and had some better fundamental knowledge going into that sprint than what I had. 

As usual, I will try to keep the things I learned in mind, but I will continue working on my issue, knowing that I do not have all the knowledge I need, and being willing to ask for help in finding it.

 

 

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

 

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

Sprint #2 Retrospective

Hello!

It’s that time of the month again, we’ve just finished up sprint number 2, and now I’ve got to write about how it went! 

I think this sprint was considerably more productive than the last one (even if I still couldn’t get my assigned issue done). I managed to parse out how I am going to make timestamps for the rabbitMQ messages, and I did a significant amount of testing with some files, to the point where I basically had everything working by the end of sprint 2. It would have been implemented were it not for the fact that I ran into some last minute errors that I couldn’t get fixed in time. Like the last post I made, the merge request will be available at the bottom of the post.

I think I did a much better job at communicating with my group this time around. I think I was a little shy before, plus overwhelmed at having to learn a new skill and be a productive member of a group. Now though, I’ve been pretty consistently talking to my group about what I’m working on, and I’ve been asking questions on things that trip me up, which I would consider a wild improvement over last time.

 In terms of things that didn’t go so well, I could do with some better time management skills. If I had planned out my work a bit better, I probably would have had ample time to fix the errors I was getting, and I might even have been able to implement everything I had been working on. I’m not going to fret about that though, I just have to keep that in mind and make sure I give this sprint all the time it needs from me to get everything done. 

As with myself, our group has been doing a lot more communicating lately. Most of it has been really good, but a good chunk of it has not been very on topic. I’m not about to be some kind of narc that wants every minute of every day be spent working, that sounds utterly miserable, but I would like more of our discussions being related to what we are working on.

After looking in the book, I think the apprenticeship pattern that relates the most to this sprint was “Expose Your Ignorance”. The pattern states that the best way to fill gaps in my knowledge is to reveal them to my group, so that I might be more encouraged to find what I am missing. I’ve been the one working on rabbitMQ for two sprints now, and as such, I think it is easy to assume that I know every aspect of what it going on, but the longer I work on this project, the more small problems seem to come out of the woodwork. Oh sure, we have the code needed to send messages, but there is no queue for them to go into, so what is the point, etc. So, had I read this pattern at the start of the sprint, I think it would have been more productive to know what kind of stuff I was missing, so I can avoid any unexpected problems. I would have laid out the plan for the sprint, done some research on everything I was doing if I wasn’t 100% solid on it, and had some better fundamental knowledge going into that sprint than what I had. 

As usual, I will try to keep the things I learned in mind, but I will continue working on my issue, knowing that I do not have all the knowledge I need, and being willing to ask for help in finding it.

 

 

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

 

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

Sprint #2 Retrospective

Hello!

It’s that time of the month again, we’ve just finished up sprint number 2, and now I’ve got to write about how it went! 

I think this sprint was considerably more productive than the last one (even if I still couldn’t get my assigned issue done). I managed to parse out how I am going to make timestamps for the rabbitMQ messages, and I did a significant amount of testing with some files, to the point where I basically had everything working by the end of sprint 2. It would have been implemented were it not for the fact that I ran into some last minute errors that I couldn’t get fixed in time. Like the last post I made, the merge request will be available at the bottom of the post.

I think I did a much better job at communicating with my group this time around. I think I was a little shy before, plus overwhelmed at having to learn a new skill and be a productive member of a group. Now though, I’ve been pretty consistently talking to my group about what I’m working on, and I’ve been asking questions on things that trip me up, which I would consider a wild improvement over last time.

 In terms of things that didn’t go so well, I could do with some better time management skills. If I had planned out my work a bit better, I probably would have had ample time to fix the errors I was getting, and I might even have been able to implement everything I had been working on. I’m not going to fret about that though, I just have to keep that in mind and make sure I give this sprint all the time it needs from me to get everything done. 

As with myself, our group has been doing a lot more communicating lately. Most of it has been really good, but a good chunk of it has not been very on topic. I’m not about to be some kind of narc that wants every minute of every day be spent working, that sounds utterly miserable, but I would like more of our discussions being related to what we are working on.

After looking in the book, I think the apprenticeship pattern that relates the most to this sprint was “Expose Your Ignorance”. The pattern states that the best way to fill gaps in my knowledge is to reveal them to my group, so that I might be more encouraged to find what I am missing. I’ve been the one working on rabbitMQ for two sprints now, and as such, I think it is easy to assume that I know every aspect of what it going on, but the longer I work on this project, the more small problems seem to come out of the woodwork. Oh sure, we have the code needed to send messages, but there is no queue for them to go into, so what is the point, etc. So, had I read this pattern at the start of the sprint, I think it would have been more productive to know what kind of stuff I was missing, so I can avoid any unexpected problems. I would have laid out the plan for the sprint, done some research on everything I was doing if I wasn’t 100% solid on it, and had some better fundamental knowledge going into that sprint than what I had. 

As usual, I will try to keep the things I learned in mind, but I will continue working on my issue, knowing that I do not have all the knowledge I need, and being willing to ask for help in finding it.

 

 

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

 

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

Sprint 1# Retrospective

 Hello!

 

This week marks the first week of sprint 2 proper, and as such I’ve been tasked with writing about my experiences with sprint 1.

First of all, I implemented RabbitMQ on the inventory backend, which took a while for me to accomplish simply because most of what we are doing in this class is so new to me. I’ll have a link to the merge request at the bottom of the page.

I think our group functioned pretty well during our class meetings, there isn’t that much I would change really. We were productive, everyone was super open to helping each other solve problems, and we laid out the plans for the sprint pretty effectively. 

I think in terms of things that didn’t go very well, I was having a ridiculous amount of problems setting up Visual Studio, and making the backend work. I should be through most of the problems now, (in theory), but during most of the setup process I was unable to build any of the frontends or the backends, which completely halted any progress I could have made early on, though it did give me a chance to read some documentation, and familiarize myself with the backend, so I suppose it wasn’t all bad.

Some things I need to work on going forward is my time management skills, as near the end of the sprint I was rushing to make all of my code work, which was very stressful. Had I managed my time better, this wouldn’t have happened, and going forward I am going to work on improving how I spend my time this sprint. 

Some things that we could work on as a group though, and even now I’m still seeing parts of this problem at the outset of sprint 2, is the fact that not everyone is checking the discord consistently, myself included. Part of the reason why I was so hesitant to join in on discussions in the discord chat was because I was everyone seemed like they already knew what they were doing, and I felt a little silly with some of the problems I was having. I am actively trying to do better, and I am regularly checking the discord and trying to vocalize my questions, but not everyone is online all the time, which makes getting them answered in a timely fashion difficult.

As for which apprenticeship pattern most aligned with this sprint, I would have to say the white belt is pretty spot on. While the context isn’t super relevant (I don’t think anyone called on my expertise), I was pretty consistently facing the problem on educating myself about RabbitMQ and Javascript, both of which I have no prior experience with. Not to mention I was almost in denial about my lack of learning, and for any trouble I was having, the blame was placed on the course load, not me, which isn’t very true. The white belt apprenticeship pattern centers around being willing to unlearn old skills if they are stopping you from effectively learning new ones, which I think was pretty relevant during this sprint. While I don’t think I would have unlearned all of my experience in Java had I read this pattern during the sprint, I think it would have tempered my expectations as to how quickly and easily I would be learning new skills. Learning Java was fairly pain free, but being under a time crunch and being forced to learn a bunch of new skills, it certainly would have been nice to have some idea of how the learning process was going to go.

 

As promised, here is the merge request I generated for this sprint:

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

 

 

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

Sprint 1# Retrospective

 Hello!

 

This week marks the first week of sprint 2 proper, and as such I’ve been tasked with writing about my experiences with sprint 1.

First of all, I implemented RabbitMQ on the inventory backend, which took a while for me to accomplish simply because most of what we are doing in this class is so new to me. I’ll have a link to the merge request at the bottom of the page.

I think our group functioned pretty well during our class meetings, there isn’t that much I would change really. We were productive, everyone was super open to helping each other solve problems, and we laid out the plans for the sprint pretty effectively. 

I think in terms of things that didn’t go very well, I was having a ridiculous amount of problems setting up Visual Studio, and making the backend work. I should be through most of the problems now, (in theory), but during most of the setup process I was unable to build any of the frontends or the backends, which completely halted any progress I could have made early on, though it did give me a chance to read some documentation, and familiarize myself with the backend, so I suppose it wasn’t all bad.

Some things I need to work on going forward is my time management skills, as near the end of the sprint I was rushing to make all of my code work, which was very stressful. Had I managed my time better, this wouldn’t have happened, and going forward I am going to work on improving how I spend my time this sprint. 

Some things that we could work on as a group though, and even now I’m still seeing parts of this problem at the outset of sprint 2, is the fact that not everyone is checking the discord consistently, myself included. Part of the reason why I was so hesitant to join in on discussions in the discord chat was because I was everyone seemed like they already knew what they were doing, and I felt a little silly with some of the problems I was having. I am actively trying to do better, and I am regularly checking the discord and trying to vocalize my questions, but not everyone is online all the time, which makes getting them answered in a timely fashion difficult.

As for which apprenticeship pattern most aligned with this sprint, I would have to say the white belt is pretty spot on. While the context isn’t super relevant (I don’t think anyone called on my expertise), I was pretty consistently facing the problem on educating myself about RabbitMQ and Javascript, both of which I have no prior experience with. Not to mention I was almost in denial about my lack of learning, and for any trouble I was having, the blame was placed on the course load, not me, which isn’t very true. The white belt apprenticeship pattern centers around being willing to unlearn old skills if they are stopping you from effectively learning new ones, which I think was pretty relevant during this sprint. While I don’t think I would have unlearned all of my experience in Java had I read this pattern during the sprint, I think it would have tempered my expectations as to how quickly and easily I would be learning new skills. Learning Java was fairly pain free, but being under a time crunch and being forced to learn a bunch of new skills, it certainly would have been nice to have some idea of how the learning process was going to go.

 

As promised, here is the merge request I generated for this sprint:

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

 

 

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

Sprint 1# Retrospective

 Hello!

 

This week marks the first week of sprint 2 proper, and as such I’ve been tasked with writing about my experiences with sprint 1.

First of all, I implemented RabbitMQ on the inventory backend, which took a while for me to accomplish simply because most of what we are doing in this class is so new to me. I’ll have a link to the merge request at the bottom of the page.

I think our group functioned pretty well during our class meetings, there isn’t that much I would change really. We were productive, everyone was super open to helping each other solve problems, and we laid out the plans for the sprint pretty effectively. 

I think in terms of things that didn’t go very well, I was having a ridiculous amount of problems setting up Visual Studio, and making the backend work. I should be through most of the problems now, (in theory), but during most of the setup process I was unable to build any of the frontends or the backends, which completely halted any progress I could have made early on, though it did give me a chance to read some documentation, and familiarize myself with the backend, so I suppose it wasn’t all bad.

Some things I need to work on going forward is my time management skills, as near the end of the sprint I was rushing to make all of my code work, which was very stressful. Had I managed my time better, this wouldn’t have happened, and going forward I am going to work on improving how I spend my time this sprint. 

Some things that we could work on as a group though, and even now I’m still seeing parts of this problem at the outset of sprint 2, is the fact that not everyone is checking the discord consistently, myself included. Part of the reason why I was so hesitant to join in on discussions in the discord chat was because I was everyone seemed like they already knew what they were doing, and I felt a little silly with some of the problems I was having. I am actively trying to do better, and I am regularly checking the discord and trying to vocalize my questions, but not everyone is online all the time, which makes getting them answered in a timely fashion difficult.

As for which apprenticeship pattern most aligned with this sprint, I would have to say the white belt is pretty spot on. While the context isn’t super relevant (I don’t think anyone called on my expertise), I was pretty consistently facing the problem on educating myself about RabbitMQ and Javascript, both of which I have no prior experience with. Not to mention I was almost in denial about my lack of learning, and for any trouble I was having, the blame was placed on the course load, not me, which isn’t very true. The white belt apprenticeship pattern centers around being willing to unlearn old skills if they are stopping you from effectively learning new ones, which I think was pretty relevant during this sprint. While I don’t think I would have unlearned all of my experience in Java had I read this pattern during the sprint, I think it would have tempered my expectations as to how quickly and easily I would be learning new skills. Learning Java was fairly pain free, but being under a time crunch and being forced to learn a bunch of new skills, it certainly would have been nice to have some idea of how the learning process was going to go.

 

As promised, here is the merge request I generated for this sprint:

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

 

 

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

Sprint 1# Retrospective

 Hello!

 

This week marks the first week of sprint 2 proper, and as such I’ve been tasked with writing about my experiences with sprint 1.

First of all, I implemented RabbitMQ on the inventory backend, which took a while for me to accomplish simply because most of what we are doing in this class is so new to me. I’ll have a link to the merge request at the bottom of the page.

I think our group functioned pretty well during our class meetings, there isn’t that much I would change really. We were productive, everyone was super open to helping each other solve problems, and we laid out the plans for the sprint pretty effectively. 

I think in terms of things that didn’t go very well, I was having a ridiculous amount of problems setting up Visual Studio, and making the backend work. I should be through most of the problems now, (in theory), but during most of the setup process I was unable to build any of the frontends or the backends, which completely halted any progress I could have made early on, though it did give me a chance to read some documentation, and familiarize myself with the backend, so I suppose it wasn’t all bad.

Some things I need to work on going forward is my time management skills, as near the end of the sprint I was rushing to make all of my code work, which was very stressful. Had I managed my time better, this wouldn’t have happened, and going forward I am going to work on improving how I spend my time this sprint. 

Some things that we could work on as a group though, and even now I’m still seeing parts of this problem at the outset of sprint 2, is the fact that not everyone is checking the discord consistently, myself included. Part of the reason why I was so hesitant to join in on discussions in the discord chat was because I was everyone seemed like they already knew what they were doing, and I felt a little silly with some of the problems I was having. I am actively trying to do better, and I am regularly checking the discord and trying to vocalize my questions, but not everyone is online all the time, which makes getting them answered in a timely fashion difficult.

As for which apprenticeship pattern most aligned with this sprint, I would have to say the white belt is pretty spot on. While the context isn’t super relevant (I don’t think anyone called on my expertise), I was pretty consistently facing the problem on educating myself about RabbitMQ and Javascript, both of which I have no prior experience with. Not to mention I was almost in denial about my lack of learning, and for any trouble I was having, the blame was placed on the course load, not me, which isn’t very true. The white belt apprenticeship pattern centers around being willing to unlearn old skills if they are stopping you from effectively learning new ones, which I think was pretty relevant during this sprint. While I don’t think I would have unlearned all of my experience in Java had I read this pattern during the sprint, I think it would have tempered my expectations as to how quickly and easily I would be learning new skills. Learning Java was fairly pain free, but being under a time crunch and being forced to learn a bunch of new skills, it certainly would have been nice to have some idea of how the learning process was going to go.

 

As promised, here is the merge request I generated for this sprint:

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

 

 

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

Sprint 1# Retrospective

 Hello!

 

This week marks the first week of sprint 2 proper, and as such I’ve been tasked with writing about my experiences with sprint 1.

First of all, I implemented RabbitMQ on the inventory backend, which took a while for me to accomplish simply because most of what we are doing in this class is so new to me. I’ll have a link to the merge request at the bottom of the page.

I think our group functioned pretty well during our class meetings, there isn’t that much I would change really. We were productive, everyone was super open to helping each other solve problems, and we laid out the plans for the sprint pretty effectively. 

I think in terms of things that didn’t go very well, I was having a ridiculous amount of problems setting up Visual Studio, and making the backend work. I should be through most of the problems now, (in theory), but during most of the setup process I was unable to build any of the frontends or the backends, which completely halted any progress I could have made early on, though it did give me a chance to read some documentation, and familiarize myself with the backend, so I suppose it wasn’t all bad.

Some things I need to work on going forward is my time management skills, as near the end of the sprint I was rushing to make all of my code work, which was very stressful. Had I managed my time better, this wouldn’t have happened, and going forward I am going to work on improving how I spend my time this sprint. 

Some things that we could work on as a group though, and even now I’m still seeing parts of this problem at the outset of sprint 2, is the fact that not everyone is checking the discord consistently, myself included. Part of the reason why I was so hesitant to join in on discussions in the discord chat was because I was everyone seemed like they already knew what they were doing, and I felt a little silly with some of the problems I was having. I am actively trying to do better, and I am regularly checking the discord and trying to vocalize my questions, but not everyone is online all the time, which makes getting them answered in a timely fashion difficult.

As for which apprenticeship pattern most aligned with this sprint, I would have to say the white belt is pretty spot on. While the context isn’t super relevant (I don’t think anyone called on my expertise), I was pretty consistently facing the problem on educating myself about RabbitMQ and Javascript, both of which I have no prior experience with. Not to mention I was almost in denial about my lack of learning, and for any trouble I was having, the blame was placed on the course load, not me, which isn’t very true. The white belt apprenticeship pattern centers around being willing to unlearn old skills if they are stopping you from effectively learning new ones, which I think was pretty relevant during this sprint. While I don’t think I would have unlearned all of my experience in Java had I read this pattern during the sprint, I think it would have tempered my expectations as to how quickly and easily I would be learning new skills. Learning Java was fairly pain free, but being under a time crunch and being forced to learn a bunch of new skills, it certainly would have been nice to have some idea of how the learning process was going to go.

 

As promised, here is the merge request I generated for this sprint:

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

 

 

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