Category Archives: CS-448

Apprenticeship Patterns Chapter 1 and Chapter 2-6 Introductions

I recently read up on different apprenticeship patterns in the book Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye. The book basically describes since aspiring software developers are like apprentices, they should focus on themselves and look for opportunities for personal development. As a software developer apprentice myself, there’s still much more I need to learn in the computer science world to strengthen my own knowledge and to apply that knowledge in the real world. Apprentices will run into problems and this book taught me about different apprenticeship patterns that I could apply to the problems I run into. These apprenticeship patterns will help anyone with shaping their mind into the right mindset to solve any problems they may run into. I did not really disagree with anything from the reading, it was more so that I found the reading was relatable since I am also starting out.

One of the apprenticeship patterns I found particularly interesting was “Emptying the Cup.” This pattern revolves around clearing your mind of everything you know and opening yourself to new and different approaches to the problem. Clearing the mind of everything you know would also get rid of the bad habits you may have picked up on when first learning the programming language, or maybe a solution to a problem that worked previously might not be the best and there might be a more efficient solution to the problem. The “Emptying the Cup” apprenticeship pattern is much like the metaphor “Thinking Outside the Box.” Rather than using traditional or old habits to solve a problem, you should drop the old habits and think differently and incorporate new perspectives to solve the problem. An apprenticeship pattern I found useful to me was “Walking the Long Road.” This pattern relates to me because I am at the beginning of the long road of my computer science career. I will hopefully learn and experience lots of new things as time goes on. Whatever happens, I will try to stay committed on the computer science path and expand my knowledge to its fullest potential.

From the blog Comfy Blog by Angus Cheng and used with permission of the author. All other rights reserved by the author.

Apprenticeship Patterns Chapter 1 and Chapter 2-6 Introductions

I recently read up on different apprenticeship patterns in the book Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye. The book basically describes since aspiring software developers are like apprentices, they should focus on themselves and look for opportunities for personal development. As a software developer apprentice myself, there’s still much more I need to learn in the computer science world to strengthen my own knowledge and to apply that knowledge in the real world. Apprentices will run into problems and this book taught me about different apprenticeship patterns that I could apply to the problems I run into. These apprenticeship patterns will help anyone with shaping their mind into the right mindset to solve any problems they may run into. I did not really disagree with anything from the reading, it was more so that I found the reading was relatable since I am also starting out.

One of the apprenticeship patterns I found particularly interesting was “Emptying the Cup.” This pattern revolves around clearing your mind of everything you know and opening yourself to new and different approaches to the problem. Clearing the mind of everything you know would also get rid of the bad habits you may have picked up on when first learning the programming language, or maybe a solution to a problem that worked previously might not be the best and there might be a more efficient solution to the problem. The “Emptying the Cup” apprenticeship pattern is much like the metaphor “Thinking Outside the Box.” Rather than using traditional or old habits to solve a problem, you should drop the old habits and think differently and incorporate new perspectives to solve the problem. An apprenticeship pattern I found useful to me was “Walking the Long Road.” This pattern relates to me because I am at the beginning of the long road of my computer science career. I will hopefully learn and experience lots of new things as time goes on. Whatever happens, I will try to stay committed on the computer science path and expand my knowledge to its fullest potential.

From the blog Comfy Blog by Angus Cheng 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.