17 August 2005

Craftsmanship patterns

All y'all ex-Noteworthy-types (and the few of you still beating the horse...) should check out Dave Hoover's Patterns of Software Craftsmanship: From Apprentice to Journeyman. It's a book-in-progress about how to be a great software craftsman (apprentice/journeyman/master), but to my mind it's more of a general-purpose "how to do the work you love and love the work you do."

(Dave's a fellow ThoughtWorker, and on a project with me at the moment, so support this book!)


kofno said...

That's good stuff. I was expecting a rehash of the Pragmatic Programmer.

tormp said...

perhaps ironically, looks like it wants to be a manual for someone who manages a software development team. software developers definitely do well to approach their work as craft, but need from management deeper appreciation of the way people become better at what they do.

why, for example, do i keep coming up against this idea that an 'architect' is someone who can make technical decisions without being directly engaged in the technology? is this ever a path to anything but bad decisions? 'resist the promotion' pattern speaks to this. it seems like, if we often experience promotions as being things that take us away from doing our jobs well, then the standard hierarchy of roles in development needs to be redesigned so that such resistance is not necessary.

russ said...

Joel's site, today, mentions his "methodology" - Big Design Up Front (BDUF), as opposed to XP which calls for design via code.

It struck me that this could be selling because of how it looks to non-developer managers. Instead of futzing around in a room with whiteboards, developers get right to coding. Obviously, that's more productive!