hi,
along the lines of a thought i've had of late "why is there so much
*code*!?", i wonder if anybody has tired to study programs and
categorize the source code into purposes, so we could get a feel for
what kinds of complexities are all mixed up in our systems? i have
done cursory google searchi
With respect to the UI portion...
Here is a paper by Myers and Rosson from 1992:
http://dl.acm.org/citation.cfm?id=142789
On Thu, Oct 6, 2011 at 6:58 PM, Raoul Duke wrote:
> hi,
>
> along the lines of a thought i've had of late "why is there so much
> *code*!?", i wonder if anybody has tired
Raoul,
along the lines of a thought i've had of late "why is there so much
*code*!?", i wonder if anybody has tired to study programs and
categorize the source code into purposes, so we could get a feel for
This is a very fundamental question.
Jorma Sajaniemi came up with one of the few ideas
>
>> along the lines of a thought i've had of late "why is there so much
>> *code*!?", i wonder if anybody has tired to study programs and
>> categorize the source code into purposes, so we could get a feel for
>
I would have thought that quite a lot of the work on "patterns" might be
relevant
