1,443 karma · joined April 13, 2014
scientist.wang
If chord changes had become more, not less popular, I'm sure that the rise of digital production would be cited as the reason, since it makes it much easier to modulate all the instruments.
I think a better hypothesis is what was alluded to in the editorial at the end:
> Say what you will about key changes. Maybe you find them at best heavy-handed and at worst trite. I know that I often do.
They have just fallen out of fashion as being gimmicky.
I don't really buy that vertical production would kill the key change. After all, beat switches are alive and well. We still have verses and choruses and interludes and beat drops.
(btw whoever invented the name "parallel key" for majors and minors with the same tonic did a terrible job)
It's an inefficient allocation of resources, since wealth brings marginally decreasing utility.
"I'm not convinced the experts know what they're talking about."
Not sure why this author thinks they know more than the experts. Confused as to why this is upvoted.
Edit: saw this other comment ( https://news.ycombinator.com/item?id=31224738 ) about how kolmogorov complexity is a bad metric and am now second guessing myself
This is fine, since most beginners consider tactics to be more exciting than strategy anyways.
As far as it relates to my comment and comment: I think you're advancing a third answer to the "why" question, not showing why "maximizing expected geometric growth" is a better "why" than "maximizing (logarithmic) utility".
With that said, I still think the "maximizing (logarithmic) utility" answer is the only good motivation. My reasoning is that most people (myself included) define rationality to be: maximizing expected utility. From this, we can derive the Kelly criterion.
I looked this up and you're right: the Kelly maximizes the expected geometric growth rate. However, the question to ask is: why do I want that? The obvious thing to want to maximize is not the expected geometric growth rate, but the expected amount of money (which it seems Kelly does NOT maximize).
The rationale to choose to maximize expected geometric growth rate is that it is equivalent to maximizing expected logarithmic utility, which is something that you actually want.
So true. Small things like this are why I'm so glad I had a software engineering job at a real company for a few years, even though I don't necessarily want to do that for life. I learned a lot from looking at codebase conventions and quick questions to the elders. Unfortunately, no one can help you with the other hard problem: naming.
There were two men trying to decide what to do for a living. They went to see a counselor, and he decided that they had good problem solving skills.
He tried a test to narrow the area of specialty. He put each man in a room with a stove, a bucket of water, and an empty pot on the stove. He said, “Boil some water in the pot.” Both men filled the pot with water from the bucket and turned on the burner to boil the water.
Next, he put them into a room with a stove, a bucket of water, and a pot full of water on the stove. Again, he said, “Boil the water in the pot.” The first man immediately turned on the burner. The counselor told him to be an Engineer. The second man emptied the pot and proudly said that now the problem is reduced to the previously solved problem. The counselor told him to be a mathematician.
This version from: https://www.davidmarcus.com/Humor/MathJokes.htm and other versions at https://www.math.utah.edu/~cherk/mathjokes.html