I was recently thinking about defining things vs explaining them. When you're trying to understand something, I think it's easier to use a story like approach. "If you take the line making a circle (or circumference if you already know that one) and measure its length. Then you take the diameter…"<p>Once you know something, it's easier to shift that knowledge into a definition. <i>"the ratio of a circle's diameter to its circumference."</i> It's more concise and is more usable to tell subsequent stories and make subsequent definitions.<p>I think this might be a common mistake when explaining things. When we understand something, it's kind of stored as a stack of definitions. "Ratio between diameter and circumference" assumes the learner knows ratio, diameter and circumference. If they don't, the tendency is to build up their definitions. <i>"Ratio is __. circumference is __. pi is__…</i>" But definitions take a bit more effort to plug into your brain.<p>I think there's a programming paradigm analogy though I'm not quite fluent enough in the concepts to be confident about it. To venture.. a declarative programming's "Case Where" expression is more difficult to grasp than procedural "if then" if you're not familiar with conditionals in general.<p>I think this is why encyclopedias can be hard to understand. They kind of define things.
The best way I've seen pi explained visually is pi-unrolled.gif: <a href="https://commons.m.wikimedia.org/wiki/File:Pi-unrolled-720.gif" rel="nofollow">https://commons.m.wikimedia.org/wiki/File:Pi-unrolled-720.gi...</a>
Another approach: <a href="http://betterexplained.com/articles/prehistoric-calculus-discovering-pi/" rel="nofollow">http://betterexplained.com/articles/prehistoric-calculus-dis...</a>