Throughout my time in the turbulent process of learning in the major of computer science there have been quite a few things that have hit me later on in the process as something I wished I had learned or read in the very beginning. The latest occurrence of this has happened with the book apprenticeship patterns. 

To start the book had a list of community values, all of which really spoke to me. Things like having a growth mindset, understanding that you can always get better and things can always improve. Believing in sharing what we know is better than trying to hoard it. The thoughts that no one tool is going to work or be perfect for everyone and a focus on individuals instead of groups.

There were quite a few more values, however those are the ones that especially resonated with me. In the beginning it took me about 3 different languages and many many hours before things started to click. Finding peers who were more experienced proved both intimidating and helpful. In this major there can tend to be a sense of elitism and as you would expect with humans, some are more helpful while others might look at you as below them. Breaking down those feelings has always come to be the first hurdle I try to get myself and anyone I’m working with over. It also ties into the sharing of what we know and there is no one perfect tool values. This also ties in the aspect of focusing on the individuals instead of an entire group. Being able to communicate and disagree and find common grounds or understandings is so important to the learning process.

Lastly, when I first started learning I was always hyper fixated on trying to understand the “best” way of doing something. It wasn’t until years later I learned that is a silly thought process to have. Sometimes it’s better to just make something work and then revisit it to try and make it better. It is all part of the process, you can get better, everything can always get better too.

Littered throughout the book are fantastic quotes to further motivation and would have given me so much more peace when recognizing my inabilities early on. Failing is an important part in learning something. My favorite excerpt from the book was a story about a master and a philosopher. While the master was trying to teach the philosopher, he kept being interrupted because the philosopher was assuming he already knew about the subject. Leaving the master with nothing to really teach. I can remember so many times where I thought I knew something and began to brush off the information I was being taught. Only to later learn how useful it would have been had I taken more time to open my mind and absorb it all, even a second or fiftieth time.

source:
https://www.oreilly.com/library/view/apprenticeship-patterns/9780596806842/#toc-start

From the blog CS@Worcester – Mike St G – 448 by Michael St. Germain and used with permission of the author. All other rights reserved by the author.

The first chapter of Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye made me think differently about what it means to be a software developer. Instead of just being a job, the authors describe it as a craft that requires continuous learning and improvement. I liked how they compared software development to traditional craftsmanship, where a person gets better over time through practice and experience. This made me realize that becoming a great developer isn’t just about getting a job, it’s about always growing and learning.

One of the ideas that stood out to me was the importance of having a growth mindset. The authors encourage developers to recognize their weaknesses and work on them instead of ignoring or hiding them. This made me think about times times when I felt uncomfortable admitting that I didn’t know something. I sometimes hesitate to ask for help because I don’t want to seem inexperienced, but this chapter made me realize that learning from mistakes and seeking knowledge is the only way to improve.

I also liked the idea of patterns, useful strategies that help developers overcome challenges in their careers. While the chapter doesn’t go into details about specific patterns yet, I think this concept is helpful. Instead of struggling alone, developers can follow advice from others who have already faced similar challenges. I usually try to solve problems on my own, but this reading made me realize that asking for guidance from more experienced developers could help me grow faster.

However, one thing I questioned was the idea that every developer should think of their work as a craft. While I agree that learning and improving are important, not everyone may want to dedicate their career to mastery. Some people may prefer to focus on specific tasks without aiming to be the best in their field. The book assumes that all developers should take the path of craftsmanship, but I think it depends on personal goals.

Overall, this chapter made me reflect on my learning process and how I approach my career. It reminded me to stay curious, be open to feedback, and actively work on my skills. It also encouraged me to look for mentors and learn from others instead of always figuring things out on my own. Moving forward, I want to take a more active approach to improving my skills rather than just learning through experience.

Link: https://www.oreilly.com/library/view/apprenticeship-patterns/9780596806842/ch01.html?_gl=1*15ilzcb*_ga*MTY4NzMxMDczMC4xNzM5MjQyNTI0*_ga_092EL089CH*MTczOTI0MjUyNC4xLjEuMTczOTI0MjgyOC4yOS4wLjA.#introduction

From the blog CS@Worcester – One pixel at a time by gizmo10203 and used with permission of the author. All other rights reserved by the author.

I just finished reading the first chapter of Apprenticeship Patterns, and I’ve got to say it’s a refreshing take on how we should think about our careers in software development. As a CS student who’s been mostly caught up in the whirlwind of lectures, coding assignments, and the occasional leet code exercise, reading this really made me think “Why did no one show me this when I first started?”.It made me rethink what it means to truly “learn” and grow in this field.

One of the coolest ideas I encountered was the emphasis on the apprenticeship mindset. Up until now, I always imagined career growth as a ladder where each step was a new certification or a harder project. But Hoover and Oshineye argue that learning isn’t about reaching a final destination; it’s more like being in a constant state of evolution, much like a traditional apprenticeship. This concept hit hard for me because it suggests that every coding bug, every failed project, and every line of messy code is just another step in the journey. It’s about continuous improvement rather than a rush to perfection.

What I found particularly intriguing was how the authors challenge the “lone genius” narrative. I used to believe that if I just buckled down and put in my ten thousand hours, I’d eventually figure it all out on my own. Now, I see the value in mentorship and community even though I’m pretty sure I’ll continue to be a bit shy about reaching out for help. It made me realize that collaboration and learning from experienced developers can be just as crucial as independent study. This chapter nudged me to consider joining more coding communities where I can both learn and share knowledge. Having the commit numbers on my GitHub page go up is starting to look like a good idea.

There were a few points I didn’t fully agree with, though. The idea that traditional schooling is almost insufficient for real growth struck me as a bit harsh. While I do see the limitations of classroom learning, I believe formal education lays an essential foundation that apprenticeships and self-directed learning can build upon. They both deserve merit and finding the right balance between both worlds can be very beneficial.

Looking ahead, I’m most excited about the chapters that dive into practical patterns for tackling everyday challenges in software development. I think those will be directly relevant as I navigate internships and open-source projects. Overall, this first chapter wasn’t just a reading assignment for me. It was a call to embrace a more holistic, reflective approach to learning. This is a mindset that I’m eager to adopt as I continue my journey in computer science.

From the blog CS@Worcester – Anairdo's WSU Computer Science Blog by anairdoduri and used with permission of the author. All other rights reserved by the author.

Reading Apprenticeship Patterns by Dave Hoover and Adewale Oshineye provided valuable insights into the mindset and journey of Software Craftsmanship. One of the most interesting aspects was the emphasis on continuous learning and humility. The book positions software development as an evolving craft rather than a static profession. The idea that mastery is never fully achieved but is instead an ongoing process aligns well with my experiences in learning new technologies and improving my coding skills.

The idea of the three stages Apprentice, Journeyman, and Master was particularly intriguing. The apprentice stage, which emphasizes building foundational skills, mirrors my own experience as I strive to expand my knowledge base. The emphasis on deliberate practice and seeking mentorship reinforced the importance of community and learning from experienced developers. The Journeyman stage’s focus on exploration and developing autonomy is something I aspire to as I work toward becoming a more independent developer.

Reading the introductions to Chapters 2-6 also offered valuable perspectives. Chapter 2’s focus on reinforcing the necessity of approaching learning with an open mind, a lesson I have found crucial when tackling unfamiliar programming problems. Chapter 3’s discussion stood out because maintaining long-term engagement in software development can be challenging. The patterns in this chapter seem particularly relevant in helping navigate burnout and staying passionate about coding.

Chapter 4, which discusses accurate self-assessment, was interesting because it highlights the importance of recognizing one’s strengths and weaknesses. Chapter 5’s introduction resonates strongly with me, as it aligns with my personal commitment to continuous improvement. The idea that learning never stops and that we must actively seek out new knowledge is a mindset I try to hold.  Finally, Chapter 6’s introduction reinforced how vital pursuing the right knowledge is important and making sure that one stays motivated to continue.

One key takeaway from these readings is that being a software craftsman is not just about technical skills but also about cultivating the right mindset and habits. Overall, this reading has inspired me to approach software development as an evolving craft, focusing on deliberate practice, feedback, and continued learning. I feel like this would be a interesting book to further reading to continue building my mental skill sets for the future.

From the blog CS@Worcester – Giovanni Casiano – Software Development by Giovanni Casiano and used with permission of the author. All other rights reserved by the author.

One aspect of the Apprenticeship Patterns reading that stuck with me was the requirements a person needs in order to be a successful software developer. A “growth mindset” as its referred to in the text is the idea that no one is born with inherent talent in a skill, its through dedication and failure that one reaches success. The growth mindset is a mindset that welcomes failure, because it teaches you to tackle the problem from a different angle. It’s the belief that something can be improved if you’re willing to put in the work despite failing. From failing, there is a lesson to be learned, from success you don’t learn anything. In a field that is constantly changing and improving, it’s crucial for a developer to have the ability to adapt to new features and languages. As a developer, you’re continuously learning how to do things more effectively than the last time, whether it be utilizing data structures or pushing out a feature. This aspect goes hand-in-hand with encouraging experimenting. Through experimenting for better solutions and failing, you get to learn why something doesn’t work or why a solution is preferable over others. On the other hand, though experimenting you might find solutions that actually improve efficiency, resulting in solutions that you can reference when solving similar problems.

Another essential aspect is pragmatic over dogmatic. It’s easier to first make a practical solution and polishing it later than trying to create a perfect solution the first time. It trains developers to think adapt when faced with changing conditions and favors optimizing for efficiency. Additionally, I think this tackles the common problem of procrastination because it allows developers to initially focus on solving the problem and disregarding how your code looks. It doesn’t matter how efficient your solution is if it doesn’t solve the initial problem in the first place.

Both of these aspects improve a developers efficiency and promotes a continuous learning routine. It allows us as developers to improve our skills and better prepares us the problems we face in the future. The rapid invention of technology today doesn’t guarantee a developers future in software, which is why we as developers must keep up with the pace and polish our skills.

From the blog CS@Worcester – Computer Science Through a Senior by Winston Luu and used with permission of the author. All other rights reserved by the author.

Reading Apprenticeship Patterns made me take a step back and think about what it really means to grow as a software developer. It’s easy to get caught up in learning new technologies, chasing certifications, and trying to keep up with the latest trends, but this book focuses on something deeper, the mindset and habits that shape a longterm career in software. One of the biggest takeaways for me was the idea that becoming a great developer isn’t about how much you already know, but about how you approach learning. The whole concept of being an apprentice, journeyman, and eventually a master makes sense, but what stood out to me the most is that there’s never really a finish line. No matter how much experience someone has, there’s always more to learn. That’s both motivating and humbling. The book also talks a lot about mentorship, self-awareness, and staying open to new ideas. It made me realize that improving as a developer isn’t just about writing more code, it’s about actively seeking feedback, being willing to unlearn bad habits, and knowing when to ask for help. I’ve always leaned towards figuring things out on my own, but after reading this, I see how valuable it is to learn from others who have been through the process. Another thing that stood out is how easy it is to fall into the trap of either imposter syndrome or overconfidence. The book emphasizes the importance of being honest with yourself, knowing what you’re good at and where you need to improve. It’s easy to feel like you’re behind when you see others moving faster, but at the same time, it’s important to not get too comfortable and stop pushing yourself. Finding that balance is key. Overall, this book challenges the way you think about growth and career development. It emphasizes the idea that learning should be intentional, that mentorship and community matter, and that real progress comes from consistent effort over time. It’s made me reflect on how I approach my own learning journey, and I’m looking forward to applying some of these ideas as I move forward in not only my career, but in life as well.

From the blog The Bits & Bytes Universe by skarkonan and used with permission of the author. All other rights reserved by the author.

In reading Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye, I found myself both inspired and challenged by the ideas presented. The book frames software development as a lifelong journey of learning and growth, rather than just a career or a set of skills. Chapter 1, in particular, resonated with me because it introduced the concept of a Software Craftsman someone who continuously hones their craft, learns from others, and embraces the challenges that come with mastery.

One of the most thought provoking aspects of Chapter 1 was the discussion on the three stages of becoming a Software Craftsman Apprentice, Journeyman, and Master. The idea that even experienced developers must remain in a constant state of learning was both humbling and motivating. I found the emphasis on deliberate practice and continuous improvement particularly useful. It reinforced the idea that success in software development is not just about accumulating knowledge but about applying it effectively, seeking mentorship, and refining skills through real-world experience.

The introductions to Chapters 2-6 provided an interesting look at the different aspects of professional growth. Chapter 2 focuses on staying humble and maintaining a beginner’s mindset, which reminded me that overconfidence can block learning. Chapter 3 emphasizes the long journey of mastery, reinforcing the idea that there is no shortcut to expertise. Chapter 4 discusses self-assessment, which I found useful because identifying weaknesses is key to improvement. Chapter 5 highlights lifelong learning, and Chapter 6 encourages taking control of one’s own apprenticeship through mentorship and self-driven education.

While I agree with most of the book’s concepts, one idea I somewhat disagree with is the notion that formal education is only a small part of a developer’s journey. While it is true that hands on experience and mentorship play a critical role, I believe that structured education still provides essential foundational knowledge. Some developers thrive with self learning, but others benefit from the structured approach that degrees and certifications offer.

The chapters that seem most relevant to me right now are Chapter 4 and Chapter 5 because I am currently focused on understanding where I stand as a developer and identifying areas for improvement. The idea that self awareness and continuous learning are key to long-term success resonated deeply with me.

Overall, I found this reading engaging, thought provoking, and practical. The emphasis on self improvement, mentorship, and hands on learning has changed the way I approach my development as a software engineer. While I believe formal education still has its place, I recognize that the real learning happens when knowledge is applied in practice. This book has given me valuable insights into what it truly means to be a Software Craftsman, and I am excited to dive deeper into the patterns in the upcoming chapters.

From the blog CS@Worcester – Software Dev Capstone by Jaylon Brodie and used with permission of the author. All other rights reserved by the author.

After reading Apprenticeship Patterns, I was left perplexed over some of the topics this book covered. To preface, I think that the authors, Dave Hoover and Adewale Oshineye, did a great job addressing how Software Development demands that individuals retain a ‘growth mindset’ throughout their studies and practice. My largest gripe is with how they frame individual progression. Hoover and Oshineye use an apprenticeship model to describe one’s progression. For starters, I believe that mastery does not exist and conflicts with the content covered in Chapter 2. The authors define mastery as “performing all the roles of an apprentice or a journeyman as well as focusing on moving the industry forward.”. Fundamentally this would be a fitting definition, as apprentices focus on learning, and journeymen focus on applying their knowledge. In practice, it can be difficult to find a balance between these two roles. Furthermore, masters are ‘pillars of knowledge’ as apprentices and journeymen refer to them for their experience. In this scenario, if the master has not found a balance between learning and practicing, then they may give ineffective or incorrect information. My solution to this dilemma is the erasure of mastery. In a field such as Software Development that is ever-changing mastery is nigh impossible to achieve. Hence, we must all dedicate ourselves to improving and finding balance between apprentice and journeyman responsibilities.

Despite having personal issues with their framework, as the content they covered in later chapters resonated with me. Chapters 3 and 4, Walking the Long Road and Accurate Self-Assessment respectively, shared ideas I agreed with the most. Chapter 3’s driving point is that we are all on the same path and that skills you see in others can be eventually learned by you. A year ago I found myself in a group of students learning Software Development. We were learning how to write tests in Java, which I had experience with from another course. In this group, we all knew the fundamentals of testing, but each of us had different skills outside of testing that we indirectly taught each other over the semester. Naturally, I was intimidated by the amount of knowledge my group members had that at the time I lacked. As the semester came to a close, that knowledge gap slowly closed as I found myself learning from seeing how they approached these problems. Chapter 4’s driving point is to not settle with your inadequacies, but to grow because of it. In this chapter, the authors suggest surrounding yourself with people who understand the material you’re trying to learn. Linux commands and Docker are some of my least knowledgeable subjects, but I chose them as my focus for this project to further develop my knowledge. Fortunately, I have been placed in a team where we all have varying degrees of skill with these subjects. I have been taking tasks involving team organization and documentation, as through writing these instructions and understanding our workflow have slowly begun to fill gaps in my knowledge.

-AG

From the blog CS@Worcester – Computer Science Progression by ageorge4756 and used with permission of the author. All other rights reserved by the author.