>Thanks to him, I'm also now a strong believer in the principle that
>whatever you want to learn about, don't study it :) 'Study' the larger
>subjects that guide the field, and 'memorize' the skills . . .
a mindset which works for me, (and which i've stolen, BTW.. i don't begin
to claim it as original to me), is: "everything is history".
whatever you want to learn, start by learning where it came from. learn
the context for each decision which was made along the path of its
development. the collective understanding of an issue over a couple
centuries tends to be much like the individual understanding of that same
issue as they become more familiar with the subject.
if you start off trying to understand object-oriented programming from
ground zero, it will seem that you're having to memorize a huge batch of
arbitrary practices and assumptions. if you study the history of software
scaling, structured programming, multi-developer programming, and the ways
compilers translate language structures into machine instructions, all that
apparently arbitrary stuff begins to make sense. you can see what
alternatives were explored, and how they took people to a point where they
needed more powerful mental tools.
mike stone <[EMAIL PROTECTED]> 'net geek..
been there, done that, have network, will travel.
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
