597 karma · joined April 12, 2013
1. Keep the HUD in focus and the road out of focus. Your eyes are still seeing a lot of road information that doesn't necessarily need the high fidelity. This is relatively safer than looking away entirely. The human brain can do a lot with scarce information.
2. Keep the road in focus and the HUD out of focus. For things like navigation this will still work fairly well since all you usually need for the navigation is the shape of the road, the direction you'll need to turn in, and how many blocks (roughly) you have until the destination. This is relatively safer than looking away at your phone or gps from time to time, or even looking around for the street names.
Realistically, people will switch between the two extremes.
On one hand I disagree because mathematics is abstraction built on top of abstraction many times over. It can be incredibly dense with information. An example comes to mind - Stokes' theorem. It's an amazingly elegant piece of math. It can be stated very neatly with 6 symbols - the integral symbol, omega, d omega, Omega, del Omega and an equal sign. If you were to unravel what each of the symbols meant using the closest terms related to them and then did the same for those terms and you continued some more, you'll have a small book.
This kind of thing is paralled in programming where you rarely want to just push bits around. I imagine you as a person who specializes in assembly complaining about the lack of rigor in more abstract languages.
However I agree with you because the above stuff is sometimes just an excuse for writing terribly. Firstly, there are practical considerations about the sheer length of text. Then you have problems of explaining. A professor writing a textbook can be far detached from that past when they first learned the stuff. My own teachers always told me to never write "obviously" unless I also explain why it is obvious (It can be very useful to explain to the student what needs to be obvious and why).
The best solution I can think of is writing with the online world in mind. A mathematical paper does not need to be short and concise. I envision two versions - the long online version and the shorted published version. There are after all practical and physical considerations in the latter while the former shouldn't be a big deal. In this way whoever is interested in more than the overview can access the longer online version and learn from it.
The biggest problem I see in this scheme is that of laziness - not everyone will want to write long texts.
This is further complicated by the fact that most subjects in math can be approached from multiple equivalent angles. For example, complex analysis can be taught from the complex derivative perspective or from the power series perspective equally well. Ideally the format of the whole thing will allow the student to naturally learn things from the angle they understand better.
Everyone can learn to read faster and everyone can claim to understand what they read. However, is that all there is to reading? There are things like imagery, sounds, feelings, etc and they can be invaluable both for the enjoyment axis and for the comprehension axis. Not to mention that I couldn't care less about your comprehension 5 minutes after the fact. Come back to me in a week and tell me how much you remember.
But let's look at these often forgotten parts of reading!
Imagery. IRL you can become over-whelmed by visual stimuli. This means there's a limited bandwidth there. Since we're mostly visual creatures there's a lot of bandwidth there but it's still quite finite(If you want convincing participate in one of those visual research experiments). When you read faster, you should expect more of this bandwidth to be taken up. As a consequence your brain will take shortcuts to minimize load and stress. It may feel like you're seeing it all but you probably aren't. It's the fast system of your brain working. The slow part of your system is taking a vacation.
Yes, you can improve your temporal resolution but not by much. Sounds are a lot like imagery.
Emotions. We are bio-chemical systems and there's a time scale over which emotions happen. They won't take place any faster. If you are like me and you care about emotions when reading, you will slow down (All I get from speed-reading is a fast-beating heart and stress quite like the stress in one of those visual labs).
Consider this. Emotions are very important for long-term memory (which is probably the most important part of reading some kind of technical text). By reading very fast you are cutting your emotions short if they happen at all. You effectively average out your emotions. It might not feel like it because you are still experiencing the peaks and valleys but they are smaller and you'll never know it. Memories are formed better when the emotions are stronger.
Speed-reading is just another phenomenon in a series of maximizations along one dimension by disregarding full the effects it has the other dimensions. Other phenomenons are known as texting, facebooking, etc. Okay, these kinds of things have their place but the more we do them, the easier it is to let them take over our lives. Our brains are not designed that way. I just find it hard to justify calling it "I read x wps" when it's more so "I lossy-scan the page and get the jist of it while stressing over my speed".
cx'(t) = a-x(t) cy'(x) = b-y(t)
You need to solve these two equations for values of c and t. The difficulty of this task depends mostly on the difficulty of the curve itself.
If the curve has equation y = f(x) (or in other words a simple representation x(t) = t and y(t) = f(x(t)) = f(t)), then you have
c = a-x cf'(x) = b-f(x)
Therefore (a-x)f'(x) = b-f(x). If f(x) is a polynomial of degree n, the problem is reduced to root-finding of a polynomial of degree n so you'll have at most n roots to deal with. So in general it won't be easy. This reduces to the code in the post if you use line segments.
Ideally you would approach this from both ends. On one end you are learning bottom up. On the other end you see what you need to make and you backtrack from there until something you know and you try to make your way up.