> Mark Levison wrote:.
> 1) Why did the manifesto get written?Others have already covered this quite nicely.
> 2) How will it help solve the problems of crap code?As an Engineering Manager, I like that the manifesto puts a name on
the broader "Craftsmanship Values" - values (and practices) that we
actively encourage and foster in our company. It also serves as a way
to clarify our expectations for potential apprentices or more
experienced developers interested in joining the team. It helps with
the mutual selection process aka hiring. The Craftsmanship Manifesto
creates a dialog which we were previously struggling to have.
Speaking more generally on the Craftsmanship Movement and how the
The Agile Manifesto states a short set of values. From those values,
Enter the Craftsmanship Manifesto. Now we have a short set of values
> 3) What will motivate "Joe: A Feature a Day" to become a craftsman?If Joe worked for me, *I* would be trying to motivate him. If Joe was
applying for a job with me, I would not hire him. A minimum
requirement to succeed on my team is a high level of interest in
learning code craft.
The Agile Manifesto served as a focal point for defining the core of
 The list has had some discussion of exactly what the "tools" are
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.