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.

Comments

Post a Comment

Popular posts from this blog

YAGNI.

Hello and welcome back to my blog! In this blog, I want to discuss YAGNI, which stands for "Ya ain't gonna need it" or "You aren't gonna need it." My professor for CS-343 briefly mentioned it in class one day and I wanted to go over it more in depth. In the past, I've done something in my projects where I should have followed the concept of YAGNI instead. I made several methods to change a variable before I actually made the main methods of what that variable would do. In the end, it turns out the methods I made were useless toward my goal and I lost a lot of time. I hope to start applying the concept of YAGNI to my future programming in order to not waste time. YAGNI is a really important concept in programming. Basically it means programmers and developers should only implement classes, methods, or whatever things they need only when they need them. By doing this, you can avoid doing unnecessary work and save a lot of time. When you think ahead and try
Read more

UML Diagrams

Hello everyone and welcome back to another week of my blog. This week I will be talking about UML diagrams. UML stands for Unified Modeling Language and it is used to model business, application structures, programming languages, analysis, design, and implementation of software-based systems. In other words, it is a way to visually represent the design and implementation of complex software. There can be many lines of codes in your software and it can be difficult to keep track of all the class relationships and hierarchies. UML diagrams can make it easier for developers to see the relationships and hierarchies. UML diagrams can work for many different programming languages. It is a standardized modeling language that any language can incorporate into the language of their choosing. There are two different types of UML diagrams. The two different types are structural and behavioral. Structural UML diagrams show how a system is structured. They show how classes and object components wor
Read more

Expose Your Ignorance

Hello and welcome back to my blog. After presenting what we did in this capstone class, the apprenticeship pattern “Expose Your Ignorance” was brought up and I wanted to check out what this pattern was. The pattern "Expose Your Ignorance" in "Apprenticeship Patterns" by Dave Hoover encourages apprentices to embrace their ignorance and actively seek opportunities for learning and growth. Rather than hiding gaps in knowledge or pretending to know everything, the apprenticeship pattern suggests acknowledging what you don't know and being open about it. Embrace the lack of knowledge and use it as a stepping stone for learning. “Expose Your Ignorance” is about normalizing the learning process. It is about showing your willingness to learn, and acknowledging that the only way to fill gaps in your knowledge is to first admit that these gaps exist. I can use this pattern in many scenarios, such as during team meetings. Instead of pretending to understand a concept, I sh
Read more