Author Archives: Andrew Lam

week-2 from the book

 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 engineering, and lifelong learning helps keep up to date on software engineering trends and technologies. It was even helping to gain more self-assurance in their skills by offering developers a collection of best practices and productivity-boosting strategies.

Those who want to become experts in software development can prepare to devote themselves to continuous learning and practice because the industry is challenged and undergoing rapid change. In this process, focused practice and reflection are both essential steps. Reflection entails taking time to pause and think about one’s knowledge and practice, evaluating what one already knows and what one may do to improve on a crucial stage in acquiring mastery since it enables the person to assess their abilities and pinpoint areas for development.

Purposeful practice and reflection lay the groundwork for domination in software development since they both emphasize enhancing knowledge and skills over time. On the other hand, deliberate practice is setting aside time to practice and hone abilities, gradually increasing over time. To attain mastery, one must engage in this kind of exercise since it makes the person pay attention to their areas of weakness and invest the time to strengthen them.

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-2 from the book

 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 engineering, and lifelong learning helps keep up to date on software engineering trends and technologies. It was even helping to gain more self-assurance in their skills by offering developers a collection of best practices and productivity-boosting strategies.

Those who want to become experts in software development can prepare to devote themselves to continuous learning and practice because the industry is challenged and undergoing rapid change. In this process, focused practice and reflection are both essential steps. Reflection entails taking time to pause and think about one’s knowledge and practice, evaluating what one already knows and what one may do to improve on a crucial stage in acquiring mastery since it enables the person to assess their abilities and pinpoint areas for development.

Purposeful practice and reflection lay the groundwork for domination in software development since they both emphasize enhancing knowledge and skills over time. On the other hand, deliberate practice is setting aside time to practice and hone abilities, gradually increasing over time. To attain mastery, one must engage in this kind of exercise since it makes the person pay attention to their areas of weakness and invest the time to strengthen them.

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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 Chapter 1 and Chapter 2-6 Introductions

Hello blog, how are you guys doing (I feel fine)? I got a book from my professors in the Syllabus. I read it; it is good. 

Even I can recommend some of my friends who are not computer science majors to these books for knowledge to develop some 

level of studying and more. 

What did you find interesting, helpful, and thought-provoking about the reading?

I found it interesting and valuable that the first two chapters, 1 & 2, stated that it is crucial to have a “growth mindset” and 

realize that learning demands perseverance, trial, and error. It was even needing to find mentors to assist in directing the learning 

process while working on a personal or side project to put newly acquired information to use. 

Also, near the end of the introduction, the second chapter points out the final four patterns that encourage continuous learning:

  • Exposing and confronting ignorance.

  • Taking on an audacious task.

  • Retreating into competence.

  • Ascending to the next level. 

Has the reading caused you to change your opinion, the way you think about the topic, or how you work?

The task does change my perspective toward the CS or related-working strategically differently from not knowing wanting to do for 

experience while approaching learning with an open mind Chapter 2. Then chapter 3, moving in to help, provide information for 

getting experience by doing side projects and reading materials. 

Even the same or new technique helps with collaboration and exceptional software developers for new learning experience journeys.

Do you disagree with something in the reading? And why? * Which chapters seem most relevant to you?

I have a minor disagreement with one of the chapters, chapter 4. The introduction of chapter 4 mentions, 

“Avoid mediocrity and self-satisfaction.” I like it when you deserve some self-satisfaction from how long you work to accomplish 

something, but I understand that there is more to learn in to-do and achieve even more than current works/projects. 

Also, the chapters that I like with the introduction are 4 for “Goal is to be better than yesterday, not just better than average.” & 

5 for “Self-discovery patterns such as Reflect as You Work, Recording and Sharing, Create Feedback Loops, 

and Learn How You Fail are also important.”

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.