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.

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.

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.

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.

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.