Structure of Epistemology (was: Joining post: 20 Years of a Science of Consciousness)
On May 25, 2012 11:10 PM, "Elliot Temple" <curi-h468vE2XxCs@public.gmane.org> wrote:
> On May 25, 2012, at 4:55 PM, brian_scurfield wrote:
> > On May 25, 2012, at 12:25 AM, Elliot Temple wrote:
> >> On May 24, 2012, at 11:22 AM, Henry Sturman wrote:
> >>> On 24-5-2012 9:53, Brian Scurfield wrote:
> >>>
> >>>> So, what is the difference between a virtual Windows PC instantiated on an iMac and an actual Windows PC?
> >>>>
> >>>> -- Brian Scurfield
> >>>>
> >>> if you look only at information output, and information output happens to be all we want from a computer,
> >>
> >> This is the wrong way to look at computer programs.
> >>
> >> Programs with the same outputs for the same input are **not the same program**.
> >>
> >> For example they may have different run times, be differently hard to re-use components of in other programs, be differently hard to add features too, and many other differences. They may be arriving at these same outputs by different internal algorithms (e.g. recursion vs iteration).
> >
> > The same knowledge can be structured in many different ways and the structure affects our ability to use and to modify the knowledge. Knowing good ways to structure knowledge is therefore important. Once again, philosophy is called for, but the field of structural epistemology is relatively undeveloped. So, what are some important problems in structural epistemology?
>
> A good place to start would be a bunch of non-programming examples and implications.
>
> Here is part of one, with some questions:
>
> We know in general terms that most school-learned knowledge is very *fragile*. That word fragile refers to its *structure*. It means that people have trouble modifying it and adapted it to different situations. It has a bad structure and is hard to use except in just the right context for it. It's not very resilient to different contexts or changes.
>
> If you don't know what I mean, look up Feynman's attempts to teach physics in Brazil. His students have very fragile knowledge and memorize a lot of stuff exactly rather than learning more general concepts.
In Physics and Math, people tend to memorize formulas; I guess cause
they think its easier. And this requires that they memorize which
formulas apply to which problems. But this means that if they are
presented with a new kind of problem, they won't know which formula to
use. And this happens a lot on physics tests. So they end up using the
wrong formulas and/or inputting the numbers in them incorrectly.
So how can someone know which formulas apply to which problems, and
what the formulas mean in order to use them correctly? He must know
the principles. They explain the meaning behind which the formulas
were created and which problems the formulas apply to; even for
problems you've never seen before. Note that the number of problems
[in physics or any other field] are infinite. So how could someone
*memorize* which formulas apply to which problems if you can't
possibly know all the problems?
This applies to all knowledge. So in physics we have principles,
formulas, and problems. I've renamed these to logics, rules, and
situations.
Consider a business environment. There are situations that employees
are presented with and they need to apply the rules that their
employers created. But without the logic, employees can not know which
rules apply to which situations. They end up applying their own logic,
which may contradict their employers logic, and that causes them to
apply the wrong rule. Or they apply the appropriate rule but they do
so incorrectly. To solve this problem, employers should explain the
logic behind the rules, so that employees can figure out which
situations to apply them and how to apply them in said situations.
> So I've described something in abstract terms but there's all sorts of more concrete issues here: how can we actually describe the structure of this knowledge directly?
All knowledge exists in one network structure. The situations can be
represented as points in an N-dimensional space. The situations'
properties define the position of the points in that space. The rules
are vectors. So the points [situations] that lie along a vector
[rule], are the situations that that rule apply to. The logics are
superstructures of vectors.
> Could we write down the ideas and diagram them and show how it's fragile and what would be a better organization?
Well most people's knowledge of physics is just rules and situations.
Its like a data table with 2 columns, one for rules and one for
situations. So they memorize which rules apply to which situations.
The issue with this is that the number of situations is infinite. So
its a futile attempt because no one can learn *all* the possible
relationships between rules and situations since the number of
situations is infinite thus making the number of relationships
infinite.
But in the network structure, the vectors [rules] apply to an infinite
number of situations because a line has an infinite number of points
[situations] along its trajectory. Note that the structure doesn't
require that the situations are known. All somebody has to do is
determine the properties of a newly-found situation [thereby
determining its position in the space], thereby determining which
rule(s) apply to it.
> What should teachers and students do differently?
Every time a student or teacher thinks about a problem, they should
discuss the principles before discussing which formulas apply to said
problem. So before solving a problem, first ask these questions:
- What principle should we be thinking about?
- How does that principle explain which formula we should use in this
type of problem?
- How does that principle explain how to apply that formula in this
type of problem?
Once the student has answered these questions correctly, then they
should continue with solving the specific problem.
> How can people fix their fragile knowledge?
Its important to relate each situation with a rule, and each rule with
a logic. But we can't be aware of all situations all the time. So we
can prioritize by paying attention to situations that we see problems
with. So say I notice a problem with a situation, I should ask:
- What rule am I following?
- What logic explains that this is the correct rule to apply in this situation?
If I can't immediately answer these questions, then there is work to
do. I can consider other similar situations or rules and try to create
an abstraction from them, thus creating a new logic. Then I can apply
that tentative logic in other known situations and rules with the aim
of finding contradictions. If I [or others] find contradictions, then
either my new logic is wrong, or it is right, which means that the
contradicting logic [the older one] is wrong.
Note that the creation of the abstraction is a guess and that looking
for contradictions is criticism.
If I do immediately answer those questions, there is still work to do.
The fact that I noticed a problem in a situation suggests that a logic
is incorrect. I can try to find the error in my logic, i.e. a
contradiction in the network structure. Once that is found, then I can
make guesses and criticisms similar to above until I've fixed the
logic thus resolving the contradiction, i.e. solving the problem.
-- Rami
RSS Feed