Pete raises significant questions about origins, training and qualifications of software developers that rub against the Software Engineering & academic "degree & credentials" theory. He proposes the craftsman model (apprentice, journeyman, master craftsman) is the better means for developing and knowing great software developers. He contrasts strongly against the IEEE folks like McConnell?, Humphrey, etc. (the whole "IEEE SWE Certification" movement)
His arguments ring mostly true to me. I'm not willing to count out computer science completely, but as a predictor for software developer success, I agree that a CS degree is little better than a button saying, "Yesterday I cudn't spel Porgramer, and now I are one!"
His thoughts on team composition and journeymen actually journeying to work with different master craftsmen of different strength areas resonates with my experiences journeying and cross-fertilizing different teams.
A provocative read. You will wind up questioning many of your "known truths" if you read McBreen. Much to argue with, and I believe he'd relish the arguement.
Recommended.
--BobLee April, 2003
![[Home]](/wiki.gif)