Recommending The Jazz Theory Book to someone starting from scratch, especially someone self studying, is like recommending CLRS or TAOCP to someone who asks "I'm curious about learning the basics of algorithms and data structures, any good books for self study?" And of course that happens all the time too. Chapter 1 is "here's what intervals like major 3rd and perfect fifths are", Chapter 2 is "here's the major scale and all its diatonic modes and ii-V-I progressions", Chapter 3 is "here's how you might use the Phyrigian mode to play over a Sus flat-9 chord" (pg 48).
Recommending Schoenberg and Messiaen as steps to get a sufficient surface of topics covered for "music theory" is performance art in its own regard. Bravo!
I IV V chord progressions and major scales are basic enough I can explain them in a 400 word post from first principles (where no music theory exists except the assertion that the human ear finds the pitch ratios of 2/1, 3/2, 4/3, 5/4, and 6/5 pleasing to the ear, that the human ear wants at least three notes in a chord, and that the human ear wants at least three chords in a progression).
Those books get very complicated very quickly, and cover music that only a relatively few people actually listen to. It was pure gatekeeping, and I’m disappointed people pointing that out were voted down. Not a good moment for Hacker News. It would be like me recommending Lisp or Forth for one’s first programming language.
[1] https://www.abrsm.org/sites/default/files/2023-09/music-theo...
Ah, well, that makes sense. I come from the "music theory is a quintessentially rigid, British-Schoolroom-coded subject that emphasizes rote memorization over actual understanding" school of thought. The musical equivalent to Americans requiring their children to recite the Pledge of Allegiance before they can even understand what the words mean.
The student seeking to build their understanding asks: why is the order of sharps FCGDAEB? Why is the mode with a sharp 4th note the Lydian mode?
Music theory responds: Because fuck you, that's why.
Same with many activities. Pedagogy and real-world use are different goals. Result is a confusing and horrible learning curve.
Maybe their needs to be a “music theory for engineers” like we have “physics for poets.”
Some people are okay with being told "memorize this list of arbitrary factoids" and there's nothing wrong with that, I'm just not one of those people who can pretend that that's good pedagogy.
I don't think rote memorization is super useful for me as a player- I've heard a lot of analysis that sounds "accurate" but often it doesn't follow my own thoughts and understandings.
If folks are playing, that raises questions about "why this here" and it's nice to have vocabulary for to understand. But I see a lot of folks (there are several in this thread) who think that is a bit backwards- that somehow folks could start with an abstract rule set and learn much. If that's the view on what is happening then I agree that "teaching theory is impossibly hard".
But if learning to play comes before the theory about why we play what we play the situation is a lot easier.
Almost all the theory I have comes from applying the stuff from "theory" books to what I do.
I learned what a secondary dominant sounds like by learning I should stay in an A chord instead of an Am in the turn around in G major blues songs long before I got the concept of what that C# might do to the local tonicity of the tune from whatever theory book.
And I think that's a reasonable way to learn: start playing whatever, try to pick up something you can read for (I read double bass and clarinet pretty well) take up a lot of piano (weather you read it or not), play a bunch with musicians, and eventually the arbitrary facts about your practice sort themselves out.