It is amazing how much less time it takes to pay off a 30 year mortgage if you increase the payments 10%. The first good many years are paying mostly just the interest.
I have a very cheap plastic one with a dial, which works amazing well for the cost (<$10). I don't remember where I bought it, but it looks like this one:
https://www.summitracing.com/parts/sum-900003
Kinetic energy is a good measure for a baseball, because essentially all of the kinetic energy is being transferred from the small object to you.
Kinetic energy is not a good measure for a car or B-52, as after the collision the large object has essentially the same kinetic energy, and a very small fraction has been transferred to you.
A bicycle is more toward the small object side, as a pedestrian is going to absorb a good fraction of the kinetic energy of the rider, which is much larger than the kinetic energy of the bicycle itself.
Modifying amplitude and phase. In the time domain you can't modify frequency amplitude without modifying the phase. If you modify just the FFT amplitude, you can end up with non-causal impulse responses.
AMA95 is one of the few Caltech classes that I still think about, mostly because it was not useful. Almost all of my other classes have been useful over the years.
I wish that the math sequence for non-math majors had included linear algebra instead.
>> makes sure to walk the trainees through the confusing states you can get into,
>> then we explain what happened, why, and how to correctly get out of them
- you don't where somewhere and you moved and you can't go back: "git reflog"
- local repo and remote with a different history (e.g: you rebased on a published branch): the whole team to sync with remote except you, then hold. Export your remaining changes as a patch. Reclone. Apply patch.
- remote has a different history than the rest of the team (e.g: you forced push a different history): Delete remote, recreate, repush from one of the team mate, then apply previous solution.
- your messed up your merge and wish to never have done that: "git reset --merge"
- the last commit is not published and you messed it up: "git commit --amend"
- the last commit is published and you messed it up: "git revert HEAD"
But rather than solve problems, better not get them in the first place. Always "git status" before anything, always get a clean working copy before checkout/pull, create a fat gitignore, etc.
Not meaningfully. It isn't written as a blog post document; it's a series of commands and presentation notes, designed to be delivered live by me. You can basically obtain what I have in the document by combining A: what I wrote above B: a good git tutorial, see internet and C: some screwing around with using git checkout, reset, and merge with commit hashes directly on a little repo you use locally.
