Add discussion of this topic to a talk?

[gaand]

See #79

[raq929]

I actually vote no on this. Or at least, no for now. This study is extremely abstract and never goes beyond the abstract. For me as a developer in WDI, the myModule examples were the most confusing and difficult to understand. I think adding in a specific example of a module that does something could be more useful. Personally I'd move from specific -> abstract.

For example, what if we wrote a module that randomizes an array? This ties it in to something we've done before, in node-api-promises, and lets them build something they feel is useful.

I would say if we change the study and it still doesn't work, then we should move it to a talk.

[gaand]

@raq929 I don't understand your objection. Discussing this topic doesn't have to be abstract. Nor does this study have to be completely abstract.

[raq929]

Sorry, I object to moving this to a talk until we try making the study less abstract and see if that works better for developers. Does that make more sense? (In other words, I agree with you that it doesn't have to be abstract, and I am arguing that if it's less abstract, it might be more effective and therefore we don't need to move it into a talk.)

[gaand]

Perhaps. I wonder if there's a benefit to having one talk that goes old school on the front end. It might help illuminate some of what's here. Or maybe we need less of this.