week-4

 Hello, here is a blog post for the fourth week; I feel stressed and relaxed simultaneously because the beginning of March is winding down for enjoyable activities and nearby spring break.

Now that I have reached the end of chapter 3, I will turn my attention to chapter 4, which discusses apprenticeship models. Throughout my reading, I found a pattern that could prove highly useful; I named it “Find Mentors.” I like this pattern because it starts with becoming a software craftsman; you first need to find mentors. You can do this by enrolling in a training course or teaching yourself independently.

This pattern is one of my favorites because it has a “recommend” option. This pattern appeals to me because it includes a “recommend” option that assists someone who needs direction and assists in making better decisions for entering the tech field or interested-related tech. This helps someone who needs advice and assists in making better decisions for entering the tech field or interested-related tech.

Nevertheless, there are some aspects of the practice that I can’t entirely agree with because there isn’t a lot of information or because it’s uncommon for somebody who needs or can’t have a mentor or guidance because there are a lot of different reasons or options when there is additional time. I like to express my disagreement with these aspects of the pattern in the following way: I could not find and have any mentors. After all, it was covid because it affects people’s attitudes, and they needed to focus on themselves rather than trying to predict what would happen next.

Have you noticed that the way you think about the work you want to do in the future or the career path you want to take as a whole has changed due to the practice?

This practice pushed me to think more about expanding my network connections to get more experience and work alongside people in the same field. For suggested action in finding mentors by signing up for an active mailing list, lurk, and seek outpatient teachers for informal advice at the next conference.

From the blog Andrew Lam’s little blog by Andrew Lam and used with permission of the author. All other rights reserved by the author.

week-4

 Hello, here is a blog post for the fourth week; I feel stressed and relaxed simultaneously because the beginning of March is winding down for enjoyable activities and nearby spring break.

Now that I have reached the end of chapter 3, I will turn my attention to chapter 4, which discusses apprenticeship models. Throughout my reading, I found a pattern that could prove highly useful; I named it “Find Mentors.” I like this pattern because it starts with becoming a software craftsman; you first need to find mentors. You can do this by enrolling in a training course or teaching yourself independently.

This pattern is one of my favorites because it has a “recommend” option. This pattern appeals to me because it includes a “recommend” option that assists someone who needs direction and assists in making better decisions for entering the tech field or interested-related tech. This helps someone who needs advice and assists in making better decisions for entering the tech field or interested-related tech.

Nevertheless, there are some aspects of the practice that I can’t entirely agree with because there isn’t a lot of information or because it’s uncommon for somebody who needs or can’t have a mentor or guidance because there are a lot of different reasons or options when there is additional time. I like to express my disagreement with these aspects of the pattern in the following way: I could not find and have any mentors. After all, it was covid because it affects people’s attitudes, and they needed to focus on themselves rather than trying to predict what would happen next.

Have you noticed that the way you think about the work you want to do in the future or the career path you want to take as a whole has changed due to the practice?

This practice pushed me to think more about expanding my network connections to get more experience and work alongside people in the same field. For suggested action in finding mentors by signing up for an active mailing list, lurk, and seek outpatient teachers for informal advice at the next conference.

From the blog Andrew Lam’s little blog by Andrew Lam and used with permission of the author. All other rights reserved by the author.

week-4

 Hello, here is a blog post for the fourth week; I feel stressed and relaxed simultaneously because the beginning of March is winding down for enjoyable activities and nearby spring break.

Now that I have reached the end of chapter 3, I will turn my attention to chapter 4, which discusses apprenticeship models. Throughout my reading, I found a pattern that could prove highly useful; I named it “Find Mentors.” I like this pattern because it starts with becoming a software craftsman; you first need to find mentors. You can do this by enrolling in a training course or teaching yourself independently.

This pattern is one of my favorites because it has a “recommend” option. This pattern appeals to me because it includes a “recommend” option that assists someone who needs direction and assists in making better decisions for entering the tech field or interested-related tech. This helps someone who needs advice and assists in making better decisions for entering the tech field or interested-related tech.

Nevertheless, there are some aspects of the practice that I can’t entirely agree with because there isn’t a lot of information or because it’s uncommon for somebody who needs or can’t have a mentor or guidance because there are a lot of different reasons or options when there is additional time. I like to express my disagreement with these aspects of the pattern in the following way: I could not find and have any mentors. After all, it was covid because it affects people’s attitudes, and they needed to focus on themselves rather than trying to predict what would happen next.

Have you noticed that the way you think about the work you want to do in the future or the career path you want to take as a whole has changed due to the practice?

This practice pushed me to think more about expanding my network connections to get more experience and work alongside people in the same field. For suggested action in finding mentors by signing up for an active mailing list, lurk, and seek outpatient teachers for informal advice at the next conference.

From the blog Andrew Lam’s little blog by Andrew Lam and used with permission of the author. All other rights reserved by the author.

week-4

 Hello, here is a blog post for the fourth week; I feel stressed and relaxed simultaneously because the beginning of March is winding down for enjoyable activities and nearby spring break.

Now that I have reached the end of chapter 3, I will turn my attention to chapter 4, which discusses apprenticeship models. Throughout my reading, I found a pattern that could prove highly useful; I named it “Find Mentors.” I like this pattern because it starts with becoming a software craftsman; you first need to find mentors. You can do this by enrolling in a training course or teaching yourself independently.

This pattern is one of my favorites because it has a “recommend” option. This pattern appeals to me because it includes a “recommend” option that assists someone who needs direction and assists in making better decisions for entering the tech field or interested-related tech. This helps someone who needs advice and assists in making better decisions for entering the tech field or interested-related tech.

Nevertheless, there are some aspects of the practice that I can’t entirely agree with because there isn’t a lot of information or because it’s uncommon for somebody who needs or can’t have a mentor or guidance because there are a lot of different reasons or options when there is additional time. I like to express my disagreement with these aspects of the pattern in the following way: I could not find and have any mentors. After all, it was covid because it affects people’s attitudes, and they needed to focus on themselves rather than trying to predict what would happen next.

Have you noticed that the way you think about the work you want to do in the future or the career path you want to take as a whole has changed due to the practice?

This practice pushed me to think more about expanding my network connections to get more experience and work alongside people in the same field. For suggested action in finding mentors by signing up for an active mailing list, lurk, and seek outpatient teachers for informal advice at the next conference.

From the blog Andrew Lam’s little blog by Andrew Lam and used with permission of the author. All other rights reserved by the author.

week-4

 Hello, here is a blog post for the fourth week; I feel stressed and relaxed simultaneously because the beginning of March is winding down for enjoyable activities and nearby spring break.

Now that I have reached the end of chapter 3, I will turn my attention to chapter 4, which discusses apprenticeship models. Throughout my reading, I found a pattern that could prove highly useful; I named it “Find Mentors.” I like this pattern because it starts with becoming a software craftsman; you first need to find mentors. You can do this by enrolling in a training course or teaching yourself independently.

This pattern is one of my favorites because it has a “recommend” option. This pattern appeals to me because it includes a “recommend” option that assists someone who needs direction and assists in making better decisions for entering the tech field or interested-related tech. This helps someone who needs advice and assists in making better decisions for entering the tech field or interested-related tech.

Nevertheless, there are some aspects of the practice that I can’t entirely agree with because there isn’t a lot of information or because it’s uncommon for somebody who needs or can’t have a mentor or guidance because there are a lot of different reasons or options when there is additional time. I like to express my disagreement with these aspects of the pattern in the following way: I could not find and have any mentors. After all, it was covid because it affects people’s attitudes, and they needed to focus on themselves rather than trying to predict what would happen next.

Have you noticed that the way you think about the work you want to do in the future or the career path you want to take as a whole has changed due to the practice?

This practice pushed me to think more about expanding my network connections to get more experience and work alongside people in the same field. For suggested action in finding mentors by signing up for an active mailing list, lurk, and seek outpatient teachers for informal advice at the next conference.

From the blog Andrew Lam’s little blog by Andrew Lam and used with permission of the author. All other rights reserved by the author.

week-4

 Hello, here is a blog post for the fourth week; I feel stressed and relaxed simultaneously because the beginning of March is winding down for enjoyable activities and nearby spring break.

Now that I have reached the end of chapter 3, I will turn my attention to chapter 4, which discusses apprenticeship models. Throughout my reading, I found a pattern that could prove highly useful; I named it “Find Mentors.” I like this pattern because it starts with becoming a software craftsman; you first need to find mentors. You can do this by enrolling in a training course or teaching yourself independently.

This pattern is one of my favorites because it has a “recommend” option. This pattern appeals to me because it includes a “recommend” option that assists someone who needs direction and assists in making better decisions for entering the tech field or interested-related tech. This helps someone who needs advice and assists in making better decisions for entering the tech field or interested-related tech.

Nevertheless, there are some aspects of the practice that I can’t entirely agree with because there isn’t a lot of information or because it’s uncommon for somebody who needs or can’t have a mentor or guidance because there are a lot of different reasons or options when there is additional time. I like to express my disagreement with these aspects of the pattern in the following way: I could not find and have any mentors. After all, it was covid because it affects people’s attitudes, and they needed to focus on themselves rather than trying to predict what would happen next.

Have you noticed that the way you think about the work you want to do in the future or the career path you want to take as a whole has changed due to the practice?

This practice pushed me to think more about expanding my network connections to get more experience and work alongside people in the same field. For suggested action in finding mentors by signing up for an active mailing list, lurk, and seek outpatient teachers for informal advice at the next conference.

From the blog Andrew Lam’s little blog by Andrew Lam and used with permission of the author. All other rights reserved by the author.

Apprenticeship Patterns: Concrete Skills

This week I continued with chapter 2 of Apprenticeship Patterns. The pattern I read was Concrete Skills. The context this pattern gives is wanting to join a talented team that can provide you with better learning opportunities than you currently have. The problem with this is the team you want to work with has no incentive to take a risk and hire someone who may not be able to contribute to the team’s work or even indirectly contribute. 

The solution to this problem is simple yet challenging. You need to acquire and maintain concrete skills. Some of the skills you will need will just be to get you past HR filters and managers that look for buzzwords when hiring. Others will be to assure your team members you can be put to good use and not need to be watched over. The skills you bring will answer the question  “If we hire you today, what can you do on Monday morning that will benefit us?” Later in your career hard skills will become less important than your reputation and your portfolio of previous work and qualities. 

The action suggestion to reach the solution is to collect the CVs of people’s skills you respect and identify five discrete skills noted. Then determine which ones would be immediately useful to the kind of team you are looking to join. Then put together a plan and a toy project to demonstrate the skills you have quired.

The reason I chose this pattern is that I am in the process of looking for a job. I want to find a good company to work for and join a team of developers where I can learn and grow not only my career but my skills as a developer. I could relate to the problem because where I am at in my career as a programmer I do not have any industry experience so I will need to do everything I can to better my odds of getting hired and being able to contribute to a team of professionals. I will have to look into taking the actions this pattern recommended in order to expand my concrete skills to the ones I will need in order to stand out to hiring managers.

From the blog CS@Worcester – Ryan Klenk's Blog by Ryan Klenk and used with permission of the author. All other rights reserved by the author.

Sustainable Motivations Pattern~

Hello!

This week, I read about the Sustainable Motivations apprenticeship pattern from “Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman” by Dave Hoover and Adewale Oshineye.

The context of the pattern is that while we’re still starting out as an apprentice, we have to explore many different things to expand our skillset. Because of this, we come across a rocky path of handling new projects with tough demands to address and things we are unsure of how to approach. Even though you have some love for your job, this exploration gives you troubles and you find yourself feeling pressured, stressed, and even doubtful of your career path.

The pattern also brings up an example of some people being trapped, wanting to move on to something else, but being held back by their motivation of money–they want to switch careers but their current job pays well. It spotlights the importance of matching up your motivations to those that will help you in the long run– to reach mastery.

The action you can make for Sustainable Motivations is to concoct a list of things that motivate you. You should then leave some time to write some additional motivations later on. You should also take the time to reflect on the motivations that you yourself really want versus what other people think. Analysis of the motivations should be done to figure out how much of these are truly what you want and which are the five most important motivators of your life. The list can be referred back to when you find yourself struggling again. 

I think that this was an interesting pattern. I do find myself doubting where I’m heading at times, especially when I face some difficult new tasks and need to branch out to something completely new to me. I like that this pattern brings up that we do find ourselves loving/feeling passionate about our job/what we’re working on, but there’s also a mix of that and being unsure of what we’re doing anymore. I find that more relatable because there’s times where I find myself loving how everything gets put together in the end, and working on certain tasks, but sometimes the process feels really discouraging. From now on, I think I’ll make a list of motivations to keep me going and know that I shouldn’t let my motivations keep me from growing as well. I think more self-analysis wouldn’t hurt. I don’t disagree with anything in the pattern. It’s a good reminder to prioritize your values and where you want to go.

From the blog CS@Worcester – CS With Sarah by Sarah T and used with permission of the author. All other rights reserved by the author.

Apprenticeship Patterns: Your First Language

This week I dove into chapter 2 of Apprenticeship Patterns and read the pattern Your First Language. This pattern was about just starting out and only understanding a little bit of one or two programming languages. I thought I would go back to the basics for this week and this pattern would be a good read for that.

The problem this pattern presents is the feeling your job or finding a job depends on your proficiency in a specific programming language. The solution the pattern gives for this problem is to pick a language and become fluent in it. It says whatever language you pick should be your main one for years and will become your default skill you work on when practicing. The pattern mentions the choice is a challenge because it will be the foundation of your early career. Some of the examples the pattern talks about for how you can work on becoming fluent in a programming language is to work on a toy application and write tests for your programs so you can understand what is going on better. A big part of this pattern was finding an experienced coder that you can work with and help mentor you and how it can make the difference in spending minutes on a problem or days. The pattern also mentions the importance of not getting stuck on only using a single language and preventing you from learning a new one.

One of the reasons I chose this pattern is because I can relate to the problem it presents. As a college senior in my last semester finding a job in the software industry will be coming up very soon. I have used several programming languages over my years of school so I have not had to focus on a single language. After reading this pattern I think java should be the language I focus on and become more fluent in because it is the one I know best already. I think I should follow the advice of the chapter and look into working on a small project so I can get better at java. Another thing I would like to do is find a mentor to occasionally help me out. I think that could be very useful for my career. Overall I thought this was a good pattern to read about and it gave me ideas of what I can do to improve my programming skills and create the foundation my career will be built on.

From the blog CS@Worcester – Ryan Klenk's Blog by Ryan Klenk and used with permission of the author. All other rights reserved by the author.

Retrospective Blog: Sprint – 1

CS@Worcester
 

CS-448
 

Sprint-1

At the end of the first sprint our team has become more united and have continually learnt how to work together. Some of the activity that I did on my gitlab include, merging and approving request as in the link https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/reportingbackend/-/merge_requests/3, https://gitlab.com/dashboard/merge_requests?scope=all&state=all&assignee_username=11kaizen this allowed the changes made to the branches of the reporting backend to be consolidataed and put into the main branch. I also used gitlab in picking up issues and checking the status of other issues that were begin worked on https://gitlab.com/groups/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/-/boards

I was really impressed of the way we communicated with each other throughout the sprint. Despite this being the first time that we worked together, for most us. We were able to have healthy communication. This helped us overcome challenges that had faced most us during the sprint. Utilizing platfroms such as discord and personal chats also allowed us to know when one of the members would not be able to make it for the class session. We also relied heavily on each other when we encountered any road blocks as we worked on the issues assigned to us. In an example, the pipeline which had a number of us stuck required almost all of us to jump on that one issue before we continued with the issues that had been assigned to us. We also shared prior knowledge especially in gitlab and its working which allowed us to all be on the same boat when it comes to saving the work that we had done using commands such as git stash among others. Also students like Anesti and Andrew who had stayed for a while since doing their software, design and architecture class were able to catch up on the structure of Thea’s Pantry thanks to assistance from all the other team members.

Generally we did well, but I belive that we could do a better job in the distribution of tasks. We could have specific people work on roles that are related, example one person could specialize in tasks related to the Api, front end or backend. Also our lack of experience cost us in minor ways such as breaking down the epics into issues and also the in the process of assigning weights of issues. We were also over ambitious as we thought that we could accomplish more issues than we acutally could. Some of us ended up taking too many issues which eventually we had to return as we couldn’t work on them all. I also realized that not most of us are not active and frequent users of Discord, some of the updates shared would be realized slightly before we met which led us to preferring to create a chat group instead.

Having completed the sprint short of the number of weights that we took, I expected myself to have closed more issues considering my understanding of the tasks at hand. I spent more time in class assisting my classmates rather than working on the issues that I had assigned myself. Also, I would have accomplished closing more issues if I had dedicated more time outside class to work on the issues that we had been assigned as a team. Now that I am now more familar with the structure and the working of the reporting system I expect myself to handle most of the issues that we had in the first sprint faster and more efficiently.

From the blog De Arrow's Webpage by Samuel Njuguna and used with permission of the author. All other rights reserved by the author.