<?xml version="1.0" encoding="windows-1252"?>
<node id="116923" title="Re:{4} Maintainable code is the best code -- principal components" created="2001-10-05 06:30:41" updated="2005-07-19 14:08:39">
<type id="11">
note</type>
<author id="41288">
jeroenes</author>
<data>
<field name="doctext">
I see what you mean.&lt;p&gt;
Want to clarify a bit, though, as I didn't say that principal 
components analysis was a good analogy. I rather said 
coding should accomplish the &lt;b&gt;opposite&lt;/b&gt;, that is
spreading to information into the functions, dividing it
equally among them.
&lt;p&gt;
However stated, the analogy goes wrong because with principal
components we talk about orthogonal vectors in space, while
with programming we have hierarchial functions.
These create a subspace of each own, and you just can not
do a PCA on different subspaces. Is that what you more or less
ment, [tilly]?
&lt;p&gt;
&lt;hr&gt;
/me notes with a smile in his face how everyone approaches
PCA from its own angle...., [Masem] from the chemical spectra
point of view, [tilly] from a encoding point of view while
I think more in pattern deviation scemes. </field>
<field name="root_node">
116172</field>
<field name="parent_node">
116807</field>
</data>
</node>
