Customer Reviews

Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman

5 star:		(8)
4 star:		(3)
3 star:		(0)
2 star:		(1)
1 star:		(1)

 

 

Being successful in IT means forever being committed to continual learning. But are there better ways to approach that learning? Are there times you get stuck when trying to move beyond what you already know? Do you find yourself somewhat fearful of moving outside your current level of expertise because you'll end up feeling stupid? Dave Hoover and Adewale Oshineye have written what I consider to be an *excellent* book on learning patterns titled Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman . Though you may think the "aspiring software craftsman" limits this to people starting out, you'd be wrong. There is so much wisdom here that I'll likely be referring back to it for years to come.

Contents:
Software Craftsmanship Manifesto
Introduction
Emptying The Cup
Walking The Long Road
Accurate Self-Assessment
Perpetual Learning
Construct Your Curriculum
Conclusion
Pattern List
A Call For Apprenticeship
A Retrospective On The First Year Of Obtiva's Apprenticeship Program
Online Resources
Bibliography
Index

The authors start by defining exactly what "software craftsmanship" entails. Among many of their thoughts, they define it as a community of practice that encompasses values such as a growth mindset, the need to adapt and change, being pragmatic instead of dogmatic, and the belief that we should share what we know instead of hoarding that knowledge. These values along with the others they talk about point strongly back to the individual's responsibility to control their own path and direction, and that's where the learning patterns come in. Instead of using a "hit or miss" method of gaining new skills, they outline a number of techniques, or patterns, which can help you maintain a level of structure to your learning, while also helping you avoid sticking points that can often derail us.

Each of the chapters focuses on a certain aspect of learning as we move up the levels of our craft. Emptying The Cup talks about how we need to approach new skills as willing beginners instead of struggling with feelings that we should know everything immediately. Learning takes time. Walking The Long Road focuses on how becoming a master in a language or skill is a long-term process. Just when you think you have a handle on something, you will look around and see others who are light-years ahead of you. But that's OK, as they have been traveling the long road just like you. Accurate Self-Assessment guides you back to making sure you measure yourself against the best (such as being the worst in a group of experts) rather than feeling you're an expert in a small pond. Perpetual Learning is just that... the constant quest to pick up new information and incorporate it into your skill base. And finally, Construct Your Curriculum helps to guide you to resources that will give you the most value for the time spent reading and learning.

This book grabbed hold of me early and didn't let go. I'm personally in the process of trying to gain some new technical skills, and I sort of wondered if I was struggling with the feeling of "being stupid" when it came to comparing what I need to know with what I already know in the Notes/Domino world. The answer to that was a resounding "yes!" Patterns such as The White Belt (setting aside my previous knowledge to learn new knowledge) and Confront Your Ignorance (pick a skill and actively fill in the gaps in your knowledge of it) made perfect sense to me as I work through my new learning. Because it's been such as long time since I was a "beginner" with a new technology, it's easy to forget these mindsets and as a result end up struggling. I appreciated being reminded of them in a way that I can actively use them again.

On a side note... It's not a stretch to look at these patterns and find that you could apply them to *any* sort of new learning. Granted, most of the commentary on each pattern is software-related, but most transcend that narrow niche. Take a skill such as writing... Most (if not all) of these patterns still apply. You don't learn how to write in three months and then stop because you've learned everything. You need to continually practice, seek out advice and mentoring from those better than you, focus on different aspects where you're weak, etc. Following these patterns in any new endeavor will greatly enhance your chances of becoming a craftsman in that area.

While this book won't teach you a new technology, it will most definitely help you learn that new technology in a way that is sustainable over the long haul. Incorporating these mindsets into your life will do wonders to make you feel much more competent, as well as helping you to enjoy the journey along the way. Apprenticeship Patterns is a highly recommended read.

"Apprenticeship patterns" was not on my Reading List, but dropped in my stack of books my accident. I decided to read the first couple of pages to see if its any good, and ended up finishing the whole book in a short time. I enjoyed reading it, it gave words to practices I've been following.

Apprenticeship patterns are patterns on how to improve your development skills over your career and gradually become a software craftsman. In consists of a bunch of chapters containing patterns. I couldn't find too much logic in grouping the patterns in this way, so myself ignored the chapter titles and just read the patterns.

The patterns have been mined and cataloged over the past 4 years. A lot of them originated from Dave's career move to software development and therefore many patterns are clarified with personal stories from Dave. They start with trivial patterns as Your First Language which gives you a start as a developer and dives into the harder ones asking you to Expose Your Ignorance and Be The Worst so that you can still learn.

My favorite pattern in the book was The Long Road which is an interesting analogy to learning forever. As eternal learners we need to learn to walk the Long (and never ending Road), as apprenticeship learning to walk the Long Road is key to continuously sharpening your skills. At least, I'll continue my journey on the Long Road.

The book is small and its a quick read. Its easy to read it in parts as it consists of patterns of each one-two pages. I was considering a 5 star rating as it is one of these books I finished in a short time because it kept me reading. Though decided to go to 4 as the book does what it does, but (as some other reviewers point out) there are also a bunch of other good software development career books.

Another amazon reviewer pointed out the craftsmanship analogy and attempt to create the new big thing in our industry. This might very well be, but I myself do enjoy the craftsmanship analogy and believe our industry is ready for a better analogy than the professional engineer one. I'd definitively recommend this book, especially for apprentices, but also for the more experienced people to provide them useful terminology for what they have probably already been doing.

As with every pattern book, SCAP captures the things that we all know are important and working in expanding one's skill and professionality. It draws a wide map of applicable patterns, showing the way to a successful technical career without being cast off to management.

The books authors have harvested the patterns in countless interviews, conversations and discussions with experienced and not so experienced software developers. So the patterns where found, refined and expanded.

What you've got in your hand is a pattern language for becoming a software professional not necessarily an "engineer" but a craftsman. Someone who not only puts technical skill but also people skills, reputation of successfully handled projects (not only development but the whole life of a software) in his pockets.

As I reviewed the book, I may add that it evolved from a loose collection of pattern to a well written intricate network (map) of profound experience.

If you are curious about the content of the book, you can always visit the O'Reilly Wiki for SCAP or Safari and have a first look at the patterns there. If you like the style then buy it.

If you have something to say or discuss, please do so in the Wiki or here.

Michael, aspiring software craftsman

I read this book for free on oreilly.com. Now I want to own a copy to add to my Software Craftsmanship library. It inspired me to write book reviews as a way of maintaining a "Reading List". It challenged me to start a website so that I can "Share What You Learn". Almost every chapter of the book has inspired or challenged me to do something. Some books you read and nod your head, this book you read and put into action.

Short, concise, well-written, highly useful. Other books such as Chad Fowler's The Passionate Programmer cover similar things, but this book sits absolutely well in that company.

This book is a series of very short articles ("patterns") around specific things you can do to guide and improve your career as a software craftsman. The articles all follow the same template: discuss the context of an environment/situation you're in, lay out a problem you need to solve, then offer up a solution for you to apply to that problem. Many of the articles are interwoven, linking common ideas or useful concepts.

This book echoes a number of things in Passionate Programmer like the concepts of being the worst in your group (work with folks that are a LOT better than you so you'll learn more), but it's a very worthwhile read on its own.

Apprenticeship Patterns is particularly nicely done in that the authors don't push a specific path they expect you to follow. They lay out a number of options and encourage you to find the path that works best for you.

I also GREATLY appreciated the authors being pragmatic over dogmatic in their approach to software craftsmanship. Certain zealots in the craftsmanship movement have completely lost site of the primary purpose of our trade: delivering value to customers. In their section "Craft over Art" he authors specifically and emphatically point out that we need to deliver "value to customers over advancing your own self-interests." They don't promote getting sloppy with one's work, but emphasize doing your work well while keeping the folks in mind who are writing the checks.

All in all, this is a solid read.

I have to say, this book is fantastic. As someone who was fortunate enough to go through a formal apprenticeship program, I see clear parallels, both with the way my formal apprenticeship was structured, and with the ways in which I strive to improve on my own. It isn't just a bunch of "You can do it" nonsense - there are clear guideposts and example goals that will all help you to become a better software developer, regardless of whether you've coded for 2 months or 10 years. Dave and Ade, thank you for writing this book.

I think this book is a must read for those starting their software career and a solid reality check for those further down the path that are pursuing craftsmanship in their career.

This book is similiar in vein to something like "My Job Went to India: 52 Ways to Save Your Job" but the India book is a lot better. The India book - ok the title is a bit tacky, but I'm sure the author didn't mean any offense, gives you more detail about how to progress in the IT field as a techie. Another comparable book is "The Productive Programmer", which is also a bit better. I'm not really sure where "Apprenticeship Patterns" really fits in, as it seems to be aimed a a book for newbies, but that's already covered by existing titles like "the Pragmatic Programmer" (this is a classic get this). But having said that there is still some good advice in it, but it's probably not the first book I'd buy to get advice for how to progress as a developer; the other 3 books mentioned in this review would be the ones I'd get.

This book is definitely one of best books I have ever read this year. On my blog, I strongly recommended it to readers of my blog. In 2002, I read "Software Craftsmanship" which made me decide to continue working as a software engineer, and this year "Apprenticeship Patterns" and "Passionate Programmer" gave me new insights on being a software engineer.

Unfortunately it is written in English. I hope the Japanese edition (translated edition) will be available soon for software engineers in Japan.

Thank you, Dave and Adewale for writing a great book.

I've worked with the author, Dave Hoover, since 2006 at Obtiva.

What is contained in Dave's and Adewale's book is many of the techniques and tools we encourage our team to use at Obtiva to grow apprentices into journeymen. We've had the opportunity to see many of our software apprentices become outstanding programmers and craftsmen over the years. Much of this success is due to what is in this book.

But, this book is more than tips on successful formal apprenticeship. Like most self-trained programmers, Dave had to construct his own apprenticeship in shops that didn't follow software craftsmanship principles. In addition to Dave's experiences, though, this book is full of supporting anecdotes from very experience programmers on how they also formed their own apprenticeships in order to become great programmers.

Ultimately, we all must forge our own path as programmers and take control of our own careers. That is what this book is about. It doesn't matter if you call it apprenticeship, software craftsmanship, or something else.