Re: Re: Programming is not a craft

>
> It also seems to confuse audiences—the people who appreciate the crafting
> of code are not the code's users. But, at the same time, well-crafted code
> benefits the users, not because it is crafted, but because it works better
> and can be changed more easily.
>
>

Yes. Then also takes a weird jab at the manifesto mechanism itself because
anyone can sign on, but then praises the agile manifesto, then calls for a
replacement to the SC manifesto. I call for a catch-22 manifesto:

The Anti-Manifesto Manifesto

We prefer creeds over manifestos, except where faith is involved.
Political manifestos are right out, let's make it law.
Authors of manifestos are inclined to hubris and thus will be the end of us;
therefore we plead the gentle reader to stay merely a reader.


... or somesuch.

I _do_ agree with Dan on the meh-ness of the SC manifesto as compared to the
Agile one:

... which I can't find - I think my brain mushed together Dan's comments
with my thoughts and this commenter's comment:

The Agile manifesto was genuinely a revelation because it explicitly valued
practices which were unusual at the time over their traditional
counterparts.


The weakest part of the SC manifesto to me is the last assertion:

Not only customer collaboration,
but also productive partnerships


 ... er, what's the difference? Then again, I'm usually called down when I
tell people a good stand up meeting is _still_ just a status meeting.


-- 
Chris
http://improvingenterprises.com
http://clabs.org