[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Standards and Namespaces - tangling two threads
Mike Champion wrote: > Stepping up to the pulpit, here's an attempt to say what 'extreme > specwriting' would imply: > > * Analysis paralysis is pointless -- There's not enough "science" now > for solid "engineering", so codify existing practice that actually works. > > * Avoid "Big Up Front Specs" - Seek to agree only on what is minimally > necessary for a business collaboration or technical interoperability. > > * Keep it simple: When it gets ugly, re-factor. Better to break the > implementations of early adopters than to have the whole effort be for > nought because nobody can understand it except the members of the > original committee. > > * Have a tight iteration cycle of specs, implementation, testing, and > refactoring/rewriting. If it causes more pain than gain, it fails the > test. Don't start with a spec, start with a test. Bill de hÓra
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|