[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Extreme Schema-building and Query-writing (was Re:[xml-dev

• To: 'xml-dev' <xml-dev@l...>
• Subject: Re: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
• From: Mike Champion <mc@x...>
• Date: Sat, 03 May 2003 10:13:58 -0400
• In-reply-to: <3EB324B9.1010009@n...>
• References: <4827EC373E03DB44AC2AB3900430896B0266FB@c...><3EB324B9.1010009@n...>
• User-agent: Opera7.10/Win32 M2 build 2840

On Fri, 02 May 2003 22:08:57 -0400, Mitch Amiano <mamiano@n...> wrote:


>> Be careful what you ask for, you might get it.
>
> AFAIK, XP isn't about giving user's what they want, it is about 
> practicing software development honestly.

I came across an interesting article making a similar point.
http://itmanagement.earthweb.com/columns/article.php/2200011
Basically, the author argues that XP is misnamed, it should be called 
"Xtremely Conservative Programming"

"1. Conservative Planning -- Plan only for the next release. Identify your 
user's most critical need and get that done first. Involve them in the plan 
so they own it and there are no surprises. Don't make a move without their 
approval; don't plan for future releases that you don't yet understand... 
2. Conservative Scope Management -- Build the smallest deliverable possible 
that gives a useful feature to your user. Put it in production immediately. 
3. Conservative vision -- Explain your design with a simple metaphor that 
everyone understands. Make sure everyone understands and accepts it before 
proceeding. If you can't illustrate your business process in terms your 
users can easily understand there is something wrong; don't bother 
starting... 4. Conservative testing -- Test everything, all the time. In 
fact, write the automated test before you even write any code... 5. 
Conservative coding -- Programmers aren't allowed to write any code without 
another programmer partner watching over their shoulder..."

Substitute "schema, stylesheet, and script development" for "coding" if you 
think this is not even potentially relevant to XML.  The first three, at 
least, could be usefully applied to XML specifications development, IMHO!

And at least 2, 3, and 4 can be applied by *users* of XML-related 
specifications:
- Use the smallest subset of the spec that lets you provide useful features
- Make sure everyone understands at least that subset of the spec before 
proceding
- Test everything with multiple implementations of the specs if you care 
about portability or interoperability.

• Follow-Ups:
  • RE: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
    • From: "Michael Kay" <michael.h.kay@n...>

• References:
  • RE: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
    • From: Jeff Lowery <Jeff.Lowery@c...>
  • Re: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
    • From: Mitch Amiano <mamiano@n...>

• Prev by Date: Re: (data) medium is the message
• Next by Date: RE: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
• Previous by thread: Re: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
• Next by thread: RE: Extreme Schema-building and Query-writing (was Re: (data) medium is the message)
• Index(es):
  • Date
  • Thread