Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

7 +/- 2 : a correspondence

1 view
Skip to first unread message

Leo Wong

unread,
Nov 9, 2006, 10:15:53 AM11/9/06
to
Readers of this news group might enjoy this exchange of letters:

http://www.rules-of-the-game.com/millernotes.htm

Leo Wong
http://www.murphywong.net

Neal Bridges

unread,
Nov 9, 2006, 5:26:00 PM11/9/06
to
"Leo Wong" <Mary...@gmail.com> wrote in message
news:1163085353.7...@h48g2000cwc.googlegroups.com...

As Miller confirms in that exchange, 7 +/- 2 is "a limit for immediate
recall", which is how it applies to Forth definitions.

--
Neal Bridges
Quartus Handheld Software
http://www.quartus.net


Krishna Myneni

unread,
Nov 10, 2006, 2:31:04 PM11/10/06
to

Thanks Leo. I enjoyed reading your subtle jab at the posters in this
newsgroup. Most of us, at one time or another, are prone to be a
"pretentious know-it-all".

Cheers,
Krishna

m_l...@yahoo.com

unread,
Nov 15, 2006, 5:58:31 AM11/15/06
to

Leo Wong wrote:
> Readers of this news group might enjoy this exchange of letters:
>
> http://www.rules-of-the-game.com/millernotes.htm
>

--quote--
the point was that 7 was a limit for the discrimination of
unidimensional stimuli (pitches, loudnesses, brightnesses, etc.) and
also a limit for immediate recall, neither of which has anything to do
with a person's capacity to comprehend printed text.
--end quote--

So, the code deserves a separate study.

But if we consider debugging and reading the code....

For code to be reviewable, the 7+-2 rule is required. (the reader must
reconstruct all relations)
(NOTE: 7+-2 relations between items rather than items themselves)

YES, THAT IS IT: the relations between code items ARE UNWRITTEN.
One has to reconstruct them each time reading the code.


For code to be just readable, 7+-2 is not required.

In particular, if the code already works, you do not need to refactor
it.
But if the code has not yet been debugged, it is meaningful to break it
into smaller parts.
(And it is meaningful to postpone refactoring till the moment it will
be really needed,
unless you feel that you still remember how the code works and it will
not be true later.)

0 new messages