[
Lists Home |
Date Index |
Thread Index
]
Mike Champion <mc@xegesis.org> writes:
> * 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.
>
>
> [speaking only for myself, needless to say]
^^^^^^^^^^^^^^^^^^^^^^^^
Which is rather unfortunate.
I would add "avoid pushing your company's products as requirements for
semi-related specs"
Ari.
|
