Re:How to read code
by telemachos on Sunday July 04, 2010 @11:03AM
(#1485776)
He mentions the small sample size (5 people) as a negative, but I wonder if this situation fits Jakob Nielsen's arguments about testing smaller groups.
Re:How to read code
by mifrai on Sunday July 04, 2010 @01:07PM
(#1485954)
Jakob Nielson argues that, specifically in usability testing, 5 people gives you a majority of your flaws but not the entire picture - where ~15 people would give you that. That is to say, more is better but there is diminishing returns. Given this, he argues that rather then expending resources to gather the entire picture for a single iteration, it's even better to test 3 sets of 5 people with design improvements between each set.
I think this argument is slightly different than just saying 5 people is enough for any sort of study. I still would have liked to seen more people. Or at least additional studies with modifications to inspect or confirm specific aspects of their findings.
Re:How to read code
by omergertel on Sunday July 04, 2010 @11:21AM
(#1485793)
I actually approve this argument. My personal experience also shows that usability testing can be done with very few people at a time, over many iterations.
Obviously, this is not a universal rule. It's useful for practical usability testing, but not for testing all cognitive processes.
Perhaps, if the variations are small enough, it may be sufficient.
That's why I prefer languages without loops.
Do you mean like Lisp which favors recursive function (or lambda calculus which uses the Y-combinator :)?
On the other hand: You can see loops as a special case of recursion. Though I like languages that don't treat this special case as a special case.
http://www.useit.com/alertbox/20000319.html
I think this argument is slightly different than just saying 5 people is enough for any sort of study. I still would have liked to seen more people. Or at least additional studies with modifications to inspect or confirm specific aspects of their findings.
http://debasishg.blogspot.com/2009/06/code-reading-for-fun-a...
http://www.oreillynet.com/ruby/blog/2006/05/post.html (section about "making Mongrels stable and secure"
http://news.ycombinator.com/item?id=483824
http://blog.rubybestpractices.com/posts/gregory/005-code-rea...
Guess loops aren't the source of ALL evil.
Reading code needs patience and getting used to the coder's style.