ineffective use of meeting time

[Spencer Dawkins]

Back to "problem space"...

I learned to code in the middle of the "structured programming/
design/ analysis" movement, where we talked about the need for a
balance between the average size of modules ("too big" is bad,
because complexity of a single large module is so high) and the
number of modules ("too many" is bad, because of intermodule
communication cost and complexity.

Any thoughts about a guess as to where we are on the balance
between number of working groups and the average size of a
working group in IETF (measured by number of working group
deliverables, not by number of participants?)?

Spencer

--- Harald Tveit Alvestrand <harald at alvestrand.no> wrote:
> 
> but the check/balance here is of course what Keith says about
> the big 
> picture - the more focused working groups more easily lose
> track of the big 
> picture (for some size of "big").
> 
> <solution-space>
> I think we need to consider how to have discussions that are
> bigger than 
> working groups but smaller than the IETF.
> </solution-space>
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com