Hunting dependencies
One of the benefits of attending lectures is that lecturers tend to give some really good unsolicited advice every now and then. Last semester, a professor of ours digressed to talk about the importance of identifying the key ingredients of a result. He’d just concluded a rather long proof, and was about to clean the blackboard as he said that the result was elementary. See, you only need this one lemma from point-set topology (admittedly a bit niche, but easy to prove), and then the definition of the Fourier transform. Put that way, sure, maybe it’s elementary. Explicitly writing down the dependencies of an idea, he said, was a good exercise.
An example #
I tried doing this a couple of times for definitions, theorem statements and proofs. At first, it felt a bit silly. Once I finished writing down the main components of a result, it seemed trivial. I overdid it at first, writing down dependencies even for minor lemmas. But for more complicated theorems or involved definitions, it proved quite useful.
Now for a concrete example. Suppose we’re trying to understand martingales. Martingales can be thought of as sequences of random variables representing fair games: if we’re given the value of the $n$:th random variable, we expect the value of the $(n+1)$:th random variable to stay the same. There’s no predictable up- or downward trend. Here’s the definition from Le Gall:
Let $(X\_n)\_{n \in \mathbb{Z}\_+}$ be an adapted, real-valued random process, such that $E(|X\_n|) < \infty$ for every $n \in \mathbb{Z}\_+$. We say that the process $(X\_n)\_{n \in \mathbb{Z}\_+}$ is a martingale if, for every $n \in \mathbb{Z}\_+$, $E(X_{n+1}|\mathcal{F}_n) = X_n$.
First, we need some terminology related to random processes, understanding what’s meant by an “adapted process” and a “filtration”. Apart from that, we need a solid grasp of conditional expectations. The definition of a conditional expectation with respect to a $\sigma$-algebra, as well as the underlying intuition. And that’s about it.
Should I bother? #
If you want to learn something thoroughly, then yes. Tracking down dependencies makes you engage more with the material. Learning a concept isn’t just a matter of being able to regurgitate the contents of the lecture notes - it requires you to build your own mental model of what’s going on. As I see it, the purpose of exercises, quizzes or review questions is to make us think more carefully about a given topic. Otherwise, because humans (or at least maths students) are lazy, chances are we’ll go through the material too quickly. Tracking down dependencies is a bit like doing more problems, in that it prompts us to revisit the material.
Another benefit of nailing down dependencies is that it makes the concept seem relatively simple. Some results can seem quite daunting at first. But working out the dependencies can make the concept seem deceptively simple - almost to the point where you’re struck with the curse of knowledge. Moreover, if I struggle to understand an idea but am clear about the dependencies, I know what to do: I’ll just read up on each of the topics involved. In this way, the dependencies translate into an a checklist for my learning process.
Lastly, I found it satisfying seeing how different notions tied into one another. I also put it all into one mindmap which, apart from having a high aesthetic value, gave me the big picture of the subject.