I whole-heartedly agree with not taking someones word for something just because of a piece of paper, or even a real-world reputation. However, in this case, the PhD in question has enough of a reputation, a body of work and a proven track record.

Add to that, my own abilities in this area were never sufficient to even begin to fully comprehend the ideas, never mind challenge them. To that end, it becomes imprudent if not impossible to "Examine what is said".

It is impossible to be fully conversant in every field, and there will always be those subject areas where you simply have to rely upon the words and skills of others. Once this point is reached it becomes a case of trying to pick the people whos words, ideas & skills you put your trust in as wisely as possible. Examining their words in the light of their peers reactions to them, and the faith they place in them, is as good a way as any I know, and better than most:)

It is an imperfect mechanism. Even the historically judged "best and brightest in their fields" tend to be superceded over time, though it tends to be in the detail rather than in any fundemental way.

That said. I never met Mandlebrot, though I did watch a live presentation he gave once (to do with fractals), and I am pretty sure that he didn't have any direct involvement in the project in question. It is quite possible that the people that performed the statistics in question misunderstood his theories, or mis-applied them. I can atest to the accuracy of the predictions that the process produced albeit over a relatively short timeframe. Being fundementally an empiricist, it is this last point that is the strongest influence upon my faith in the methodology used.


Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.


In reply to Re: Re: Re: Re: Re: Re: Re: Software Design Resources by BrowserUk
in thread Software Design Resources by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.