Author Archives: Camille

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.

Software Craftsmanship

 Hello!

 I’ve had a bit of assigned reading to do for my capstone course, ans as such, I thought it would go the way of most readings of that ilk; incredibly dry and ungodly boring. But surprisingly I had a pretty good time with Apprenticeship Patterns by Dave Hoover and Adewale Oshineye. 


The text captures something that I find to be incredibly important to the process of becoming a career programmer, the ability to be flexible. Much of my time spent learning to program has consisted of how to do things, but never why or when we should do them. Sometimes it feels like I have a fairly full toolbox, but I don’t have the required knowledge to apply my tools in ways they weren’t explained to me in. I’ll admit, this is more of a personal failing I feel, but the point still stands. 


Chapter 1 and the introductory paragraphs to Chapter 4 really stood out to me the most, as Chapter 1 goes into detail about what it means to be a craftsman, and an apprentice. It highlights the experiences one might go through, and what one might expect to get out of an apprenticeship, but the most compelling out of that chapter was the focus on the need to continue learning. In order to be a good apprentice, and get anything meaningful out of the experience, it takes a want to learn how to become a master, and the willingness to continue to developing your craft, and focusing on how you can improve your mindset and workflow. Chapter 4 stood out to me with it’s anecdote about Dave’s experience with certifications, and his discarding of them as he learned from a group of Perl hackers. Not only was it quite amusing, it highlights ths importance of a flexible mindset. None of us are ever done learning, and in order to ever become a master, you cannot be satisfied with jist maintaining the status quo.

 

Overall I found the selected chapters to be genuinely pretty inspiring, and it put into perspective where my head is at in terms of my software development journey, and how I might go about improving them. This might be optimistic, but this book might end up being one I read in my off time, a rare feat for an assigned reading of this nature.

 

 

 

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

Test Test Test Redux

 Hello!

 

I’m still Camille and this is still my blog, I guess!

 

CS443

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

Software Craftsmanship

 Hello!

 I’ve had a bit of assigned reading to do for my capstone course, ans as such, I thought it would go the way of most readings of that ilk; incredibly dry and ungodly boring. But surprisingly I had a pretty good time with Apprenticeship Patterns by Dave Hoover and Adewale Oshineye. 


The text captures something that I find to be incredibly important to the process of becoming a career programmer, the ability to be flexible. Much of my time spent learning to program has consisted of how to do things, but never why or when we should do them. Sometimes it feels like I have a fairly full toolbox, but I don’t have the required knowledge to apply my tools in ways they weren’t explained to me in. I’ll admit, this is more of a personal failing I feel, but the point still stands. 


Chapter 1 and the introductory paragraphs to Chapter 4 really stood out to me the most, as Chapter 1 goes into detail about what it means to be a craftsman, and an apprentice. It highlights the experiences one might go through, and what one might expect to get out of an apprenticeship, but the most compelling out of that chapter was the focus on the need to continue learning. In order to be a good apprentice, and get anything meaningful out of the experience, it takes a want to learn how to become a master, and the willingness to continue to developing your craft, and focusing on how you can improve your mindset and workflow. Chapter 4 stood out to me with it’s anecdote about Dave’s experience with certifications, and his discarding of them as he learned from a group of Perl hackers. Not only was it quite amusing, it highlights ths importance of a flexible mindset. None of us are ever done learning, and in order to ever become a master, you cannot be satisfied with jist maintaining the status quo.

 

Overall I found the selected chapters to be genuinely pretty inspiring, and it put into perspective where my head is at in terms of my software development journey, and how I might go about improving them. This might be optimistic, but this book might end up being one I read in my off time, a rare feat for an assigned reading of this nature.

 

 

 

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

Software Craftsmanship

 Hello!

 I’ve had a bit of assigned reading to do for my capstone course, ans as such, I thought it would go the way of most readings of that ilk; incredibly dry and ungodly boring. But surprisingly I had a pretty good time with Apprenticeship Patterns by Dave Hoover and Adewale Oshineye. 


The text captures something that I find to be incredibly important to the process of becoming a career programmer, the ability to be flexible. Much of my time spent learning to program has consisted of how to do things, but never why or when we should do them. Sometimes it feels like I have a fairly full toolbox, but I don’t have the required knowledge to apply my tools in ways they weren’t explained to me in. I’ll admit, this is more of a personal failing I feel, but the point still stands. 


Chapter 1 and the introductory paragraphs to Chapter 4 really stood out to me the most, as Chapter 1 goes into detail about what it means to be a craftsman, and an apprentice. It highlights the experiences one might go through, and what one might expect to get out of an apprenticeship, but the most compelling out of that chapter was the focus on the need to continue learning. In order to be a good apprentice, and get anything meaningful out of the experience, it takes a want to learn how to become a master, and the willingness to continue to developing your craft, and focusing on how you can improve your mindset and workflow. Chapter 4 stood out to me with it’s anecdote about Dave’s experience with certifications, and his discarding of them as he learned from a group of Perl hackers. Not only was it quite amusing, it highlights ths importance of a flexible mindset. None of us are ever done learning, and in order to ever become a master, you cannot be satisfied with jist maintaining the status quo.

 

Overall I found the selected chapters to be genuinely pretty inspiring, and it put into perspective where my head is at in terms of my software development journey, and how I might go about improving them. This might be optimistic, but this book might end up being one I read in my off time, a rare feat for an assigned reading of this nature.

 

 

 

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

Software Craftsmanship

 Hello!

 I’ve had a bit of assigned reading to do for my capstone course, ans as such, I thought it would go the way of most readings of that ilk; incredibly dry and ungodly boring. But surprisingly I had a pretty good time with Apprenticeship Patterns by Dave Hoover and Adewale Oshineye. 


The text captures something that I find to be incredibly important to the process of becoming a career programmer, the ability to be flexible. Much of my time spent learning to program has consisted of how to do things, but never why or when we should do them. Sometimes it feels like I have a fairly full toolbox, but I don’t have the required knowledge to apply my tools in ways they weren’t explained to me in. I’ll admit, this is more of a personal failing I feel, but the point still stands. 


Chapter 1 and the introductory paragraphs to Chapter 4 really stood out to me the most, as Chapter 1 goes into detail about what it means to be a craftsman, and an apprentice. It highlights the experiences one might go through, and what one might expect to get out of an apprenticeship, but the most compelling out of that chapter was the focus on the need to continue learning. In order to be a good apprentice, and get anything meaningful out of the experience, it takes a want to learn how to become a master, and the willingness to continue to developing your craft, and focusing on how you can improve your mindset and workflow. Chapter 4 stood out to me with it’s anecdote about Dave’s experience with certifications, and his discarding of them as he learned from a group of Perl hackers. Not only was it quite amusing, it highlights ths importance of a flexible mindset. None of us are ever done learning, and in order to ever become a master, you cannot be satisfied with jist maintaining the status quo.

 

Overall I found the selected chapters to be genuinely pretty inspiring, and it put into perspective where my head is at in terms of my software development journey, and how I might go about improving them. This might be optimistic, but this book might end up being one I read in my off time, a rare feat for an assigned reading of this nature.

 

 

 

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