Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Why a manifesto? How... Help shape the InfoQ news item
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rik Dryfoos  
View profile  
 More options Mar 11 2009, 4:02 pm
From: Rik Dryfoos <rdryf...@gmail.com>
Date: Wed, 11 Mar 2009 13:02:44 -0700 (PDT)
Local: Wed, Mar 11 2009 4:02 pm
Subject: Re: Why a manifesto? How... Help shape the InfoQ news item
> 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
manifesto relates - it is obviously written as an extension of the
Agile Manifesto. I think it works this way too.

The Agile Manifesto states a short set of values. From those values,
we can decide to use tools such as two-week iterations, continuous
integration, short feedback cycles, Pairing and TDD. With the
exception of TDD, these tools focus on the environment within which a
developer operates and do not really address "how" a developer writes
her code.

Enter the Craftsmanship Manifesto. Now we have a short set of values
from which we may decide to employ tools [1] such as;  Uncle Bob’s
SOLID principals [2], DRY, YAGNI, KISS, Knowing how to recognize and
refactor code smells, Good Naming and Self-Documenting Code.

> 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
what became the Agile movement. I hope that the Craftsmanship
Manifesto will serve a similar function. It has the potential to spark
discussion, crystallize thoughts and spread awareness. Just as with
Agile Manifesto, the Craftsmanship Manifesto promises to lead to more
profitable businesses and more enjoyable work for everyone on a
software development team.

Sincerely,

Rik Dryfoos
Engineering Manager, Development

Didit
55 Maple Avenue, Suite 106
Rockville Centre, NY 11570
P: 516-255-0500/1-800-932-7761
E: rik.dryf...@didit.com
www.didit.com

Didit is...
Ranked #137 in the Inc 500 for 2007
Ranked on Deloitte Technology Fast 500 for 2007 & 2008

FOOTNOTES

[1] The list has had some discussion of exactly what the "tools" are
that a Craftsman uses. I am using "tools" as I understand them and
others may very well see this differently.

[2] http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod


 
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.