🚀 go-pugleaf

In "human factors in computing systems" - CHI'89 conference proceedings
pp 69-74, There is an interesting paper by Beth Lange and Tom Moher
of the Univ. of Illinois at Chicago concerning a study of reuse
by a objective-C programmer. The paper identifies strategies that were
used and  discusses 'comprehension avoidence' or avoiding deep understanding
of details.

The subject was experienced in the use of ICpak201. She relied mostly
on a copy/edit methodology where a sibling or superclass served as a
template. Adjustments were made method-by-method in a linear fashion
and verification was done empirically through symbolic execution.

Is this a good representation of object oriented programming in general?
Are there any comments, rebuttals, or flames?