Kevin Smith wrote:
If I may interject some opinions on process...
Sure, it's es-discuss. Plus, you've earned your spurs.
I'm not sure how this fits in with the new post-ES6 process, but from
this one outsider's point of view:
- A formal set of design goals should be completed and agreed upon
before design work is begun. The design goals form the basis of
measurement and the champion(s) must be bound to them at all times.
Any changes to the design goal document must be carefully reviewed in
order to prevent churn. A detailed change-log is an obvious requirement.
Sounds both good in principle, and bad like waterfall. Waterfall is dead.
Would such goals have helped promises? I bet we would have fought over
the goals, at best. At worst, we'd agree to vague goals and end up where
we ended up.
- A *working* implementation should be created and solutions to
real-world use cases should be programmed using the design before any
spec language is authored. Spec-language is a poor medium for
communicating both design intent and programming intent.
Yes, this.
On a side note: it seems to me the the existence of the design
champion, who by definition is deeply invested in the design process,
implies the existence of its dual: the anti-champion, who is detached
from the details of the design work and provides a vital holistic
perspective.
Yes, the _advocatus diaboli_. We have plenty of those, though. Too many,
at this point.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
