Andrew Lam’s little blog

 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 enterin

Hello, a blog for the third week; it seems cluttered because I am almost done with school since this is the end of February. Anyway, I'm starting to read chapter 3 for apprenticeship patterns. While reading, I found one of the helpful patterns was “ Sustainable Motivations .” It has a set of motivations that can withstand the inevitable challenges and difficulties in pursuing a particular craft or profession. In the context of software development refers to a group of internal and external factors that keep software developers motivated and engaged in their work over the long term. Sustainable motivations can vary from person to person. Still, some common examples include a passion for programming, a desire for mastery, a sense of purpose, financial stability, social recognition, and a positive work-life balance. Even characteristics of sustainable motivations are resilient, flexible, and adaptive, allowing developers to overcome obstacles, stay committed to their craft, and contin

 Hello, a blog for the second week; it seems nice and claims a little bit. I'm starting to read chapter 2 for apprenticeship patterns. While reading, I found one of the helpful patterns was “Record What You Learn.” It is nice to look back at the progress from the start and end with some struggles for learning something every day to help keep track of things that progress to improve at working efficiently. There is another pattern I would like to disagree with my opinions is “Reflect as You Work”; because it made me have doubts like “why didn't I do this earlier or how couldn’t I think of it.” regardless, it is nice to see what you have to learn, and done for this to work. Has the practice caused you to change how you think about your intended profession or how you think you will work? For developers of these practices, it helps for using the patterns from this book can have several benefits. One of the benefits was to advance their understanding and proficiency in software engi