Blog Post for Chapter 1 and 2 – 6 Introduction

During the second week of the Spring Semester, I read the book “Apprenticeship Patterns” especially chapter 1 and introductions of chapters 2 through 6 by Dave Hoover and Adewale Oshineye. This book tends to be very interesting for me so as I was asked just to read the introduction I did that but I will read the whole book later on. I like the way how the author assigns software development more like a craft than a skill. As it turns out if a person comes up with an idea for creating some kind of craft and if the same happens when it comes to software development that means he/she has successfully designed software on their own using different tools and resources. That being said, I think programming must be taken more like a skill as making a craft than just getting assignments and exams done and getting the training certificate or degree certificate. Collaboration with experts as students will face with experts is more meaningful than just books and assignments. I like the story of a person named Dave in chapter 3, in the beginning, he seems to be much less experienced than he is now although he had so many training certificates and achievement certificates hanging in his cubicle. Later as he joined the hacker group, he realized that he was just scratching the surface of software development. Later as time passed, he pushed himself into side projects as he was inspired by hackers’ abilities. Later on, as he learned more from the hackers he started collaborating face-to-face with other exceptional software developers, and although they were ahead of him, they went walking the same road. The moral is if you follow the experts and learn from them it will be more beneficial than just achievement and training certificates. I have one of my friends who can relate almost the same to Dave in the story. He also follows smart people even if he/she is a hacker and gathers ideas from them and implements their ideas for a better outcome. The other interesting introduction was chapter Four “Accurate Self-Assessment” , it has been said that it is one of the human behaviors to just get knowledge on how much is needed rather than going above average. In the field of Software developer, one’s goal must just not be to be an average developer but to measure your abilities and see what you know today and then compare it with yesterday and try to make it much better today compared to yesterday. It is also very important that you should compare yourself to what you were yesterday than comparing yourself with other people, doing this will help you grow over time and also can help you become a successful developer.