Hi, that's exactly the kind of problem that was going on through my mind for about 2 weeks now. We've never learned howto analyze whitepapers or dissertations.

Hi, that's exactly the kind of problem that was going on through my mind for about 2 weeks now. We've never learned howto analyze whitepapers or dissertations. Let alone howto convert an unknown mathematical formula into usable code. I see this as one of the most essential skills we never learned. Could someone please teach that skill? =)) I'd be very grateful if someone could help me and others understand how to dissect and codify the main point of a whitepaper. This is a very interesting paper for example, that I've tried to understand, but I still only have a vague idea of it: http://pages.cs.wisc.edu/~jyc/papers/fibonacci.pdf http://pages.cs.wisc.edu/~jyc/papers/fibonacci.pdf Here http://groups.csail.mit.edu/netmit/sFFT/ http://groups.csail.mit.edu/netmit/sFFT/ is another very interesting algorithm I knew for a long time, but even though I understand the principle. And tried to put it into code, I wasn't able to identify what the important part of their whitepaper is. They even provided some pseudo-code which I've seen in many other papers, but I've never seen where and how they standardized the pseudo-code notation. The pseudo-code looks ambiguous to me. (NOTE: They provide the code now, but that wasn't the case when the paper was published first). This kind of thing makes me feel stupid.