It's relatively easy to read music theory notation, so that the Gibberish and Goobeltygookus make sense, similar to learning mathematical notation. (I personally believe this is easier than learning the alphabet, but that's a different story)
However, understanding what the abstractions mean is difficult. The difference between memorizing formulas and intuiting patterns. Maybe this is no harder than understanding the abstractions behinds words.
Like most "hard" things, the largest reason for difficulty is one of obtaining persistent practice.
If it were common to sing piano music using theory words rather than a single "lalala", for example, or if our language made use of specific tonal changes (up a second v down a major third), or if everyone learned the theory at the age where we now learn the alphabet, the gibberish goobeltygook would seem "easy".
Someone on HN is going to hammer me. I just muddled through the ambiguity.
Then again, what I used to think was the real solution (an exensible grammar -- say, s-expressions -- which would remove the ambiguity) would result in really ugly-looking math.
[Don't get me started on denotational semantics. I tried, I really tried to understand the foundation of Standard ML through some DS-based books on the subject, but in the end I just got sick of yet another system of poorly defined heiroglyphics. Maybe I'm just allergic.]
One note from the excellent introduction focused how to learn math (q.v.): "In his book on mathematical pedagogy [15], Hans Freudenthal argues that the reliance on ambiguous, unstated notational conventions in such expressions as f(x) and df(x)/dx makes mathematics, and especially introductory calcu- lus, extremely confusing for beginning students; and he enjoins mathematics educators to use more formal modern notation."
Plus, Lisp!
In contrast, the essence of music theory is fairly easy (if you have a math background, you could learn it in a few hours!). But music notation a strange mix of time-tested, concise notations with cruft that remains due to backwards compatibility.
So we write "饾啴" to mean pedal down, but "饾啹" to mean pedal up. We write C7, Cmaj7 and Cmin7 but the modifiers "maj" and "min" modify different parts of the chord. And so on.
And sometimes the notation is there, but people simply don't use it consistently. For instance, the usage of 6th and 13th interchangeably without proper justification (e.g. the post in question).
In fact, in the history of jazz piss poor black kids that never went to school managed to master music theory just fine. And an enormous amount of people all around the world.
The particular example you mention (chord naming) has something like 1/100 the difficulty of something like regular expressions.
And it's several orders of magnitude easier than actually learning to play your instrument. Which also millions of people manage to do.
I'm not sure who the article was for, people who already know its contents perhaps? Anyone else would have to have a solid background in theory to understand much of anything in it.
"I find not only the 13th chord a great substitute for a 7th now, especially when it's the dominant resolving to the tonic, but I also love the 7th+3rd+13th/6th way of voicing it too."
No, just anyone who already knows a bit of music theory. Not even a great deal of it. Something that can be learned in a week, tops.
Tons of articles on HN have titles like: Djikstra's algorithm, advanced types in Haskell, currying and memoization in Scala, A Graphical Notation for the Lambda Calculus, and similar content.
Is someone expected to understand those without knowing the underlying naming schemes, theory, basic domain knowledge etc?
Or do people seeing stuff like "^[ab](foo)^[k])/i complain that:
"that pretty much explains why people have a hard time "getting" computer science theory. Gibberish.Goobeltygook$"?
There a logic behind regular expressions, and there's a logic behind chord/interval notation. And the second is a lot easier, too, and it's used because it's succint and it works.
Urban legends about qwerty keyboards ( http://www.utdallas.edu/~liebowit/keys1.html ) and railroad gauges ( http://www.snopes.com/history/american/gauge.asp ) aside, bad solutions don't last 400 years.
"""Anyone else would have to have a solid background in theory to understand much of anything in it."""
The naming scheme used in the article takes like 10 minutes to grasp --and requires no great background in music theory. 7th, 13th etc are like numeric indexes.
As for dominant / tonic, those are are like music theory 101. Similar to knowing what "Objects" and "Interfaces" mean when discussing OO programming.
Usually such articles are praised on how well-written they are, even allowing for people not familiar with the background getting the gist, somewhat.
> Or do people seeing stuff like "^[ab](foo)^[k])/i complain that:
> "that pretty much explains why people have a hard time "getting" computer science theory. Gibberish.Goobeltygook$"?
> There a logic behind regular expressions, and there's a logic behind chord/interval notation. And the second is a lot easier, too, and it's used because it's succint and it works.
That's a very good example, because IMO it demonstrates my point. If anyone would have written an article like that about regular expressions, written in the same way, with:
Regexes peppered inline throughout each sentence, repeatedly mentioning how this is probably the most basic stuff ever--up to the point of actually apologizing for stooping down to the level of what must probably be "regex theory 101". Then someone would have remarked "that pretty much explains why people have a hard time 'getting' regular expressions. Gibberish. Goobeltygook", then nobody would have disagreed with them. Because everybody knows that a badly written article about regexes very quickly becomes to look like unreadable gibberish.
And in case you didn't catch that, this article actually apologizes for "probably being jazz theory 101". What? Have you ever seen a comp.sci/math article being apologetic about saying
"I know this is probably graph theory 101, but we define a graph as an ordered pair G = (V, E) comprising a set V of vertices or nodes together with a set E of edges or lines ..."
Of course not! It is considered good style to repeat the basics, and in fact IMO, I consider it bad style to be apologetic about it (because it's condescending to that part of your audience that made good use of the quick refresher).
Everybody knows that regexes can quickly look like unreadable gooblygook, even if you're familiar with them, and any article that wants to discuss something fundamental about regexes, is going to have to take some special care to not make it look as such. In some sense, same goes for set theory or mathematical formulae in general.
That still doesn't mean the hypothetical regex article would be so much clearer to the layman, but it would seem much more approachable, in some sense.
I thought I knew some very rudimentary things about music theory, but apparently not enough to make the leap to "get" and string together what this guy is talking about in pure jargon (and believe me I spent more than the "10 minutes" everybody says it would take). To me, that tells me the article is simply badly written. A similar exposition about monads in functional programming, is more like what I'd expect in a 1-on-1 comment thread (when it's perfectly ok to use as much jargon to succinctly get your point across) than a blog article intended for the general public (when regardless how obvious or simple, it always pays to step down and explain from basics, even if only to reinforce the audience that already knows them you're talking about the same things).
In fact, the only other computer science topic I've seen this sort of attitude, is the security/exploit/disclosure/hacking scene. That's where people routinely bash on eachother for repeating the basics and that "this is nothing new" because hacker X already did sploit Y in 2005 which was kinda similar (regardless that writing/warning about it again is a good thing).
I maintain, however, that people without sufficient background in music theory have a right to complain (on HN, not on your blog) it's quite incomprehensible. And that it could have been written to better accommodate for that. Not that you have any obligation to, as you said it's a personal blog post where you can write whatever you want, however you want :)
Though personally, if you would put in a few links to some simple introductory articles--maybe the other commenters were right and it just takes 10 mins of reading the right definitions of notation, maybe I just read the wrong things before or forgot the important parts--that would have definitely triggered me to explore some more of the subject matter, and you can't disagree that would have been a good thing ;-)
They are not difficult to understand, and they are even easy to derive from some basic rules.
But you do have to remember them, not derive them at will, to be able to think musically and play fluently.
I think that's my problem with Chemistry too, as opposed to Physics. There was always tons of stuff to remember when studying chemistry, while just remembering a few basic rules and deriving everything else was possible in Physics (I talk about High School grade material, of course).
You can look at a diagram that will tell you what notes go together to make a particular 11th chord, say, but it tells you nothing about why that's a useful way to combine notes.
The blog post is aimed at people who know some of the "what", but who could use a clue as to some of the "why".
It is the conceptual framework & vocabulary you use to talk about music, not perform it.
If kids love performing and listening to music, they'll want to talk about it. And initially they'll be limited to things like "I love that thing it does near the middle when the bass is going baBONG baBONG baBONG then everything suddenly get really quiet and strange".
That's obviously ridiculously imprecise, right? And aren't you curious to know what "strange" means in this context? Suppose you want to write a piece of music that sounds "strange" like the piece you liked, but more so? So even piss-poor black kids end up with a thirst for a subject that looks pretty dry to the unmotivated.
Here's a delightful example:
http://www.thestar.com/entertainment/article/1090345--video-...
We're talking about music theory in genres where it is important, i.e where the music is involved and advanced. Three minute fifties rock-n-roll tunes is not where this happens.
Little Richards is great, but not in the musically advanced way Charles Mingus, Miles Davies, etc are great. He's great for the raw fun/energy/danceability impact of his music.
So, not really a counter-example.
It's ironic that you would pick a couple of jazz musicians to illustrate this, since for most of its formative history jazz was derided as a vulgar form. Only in later stages was it championed by the priests of "advancedness". This is a sign of decadence. When the Davises and Minguses appear, that is the late-blooming of a genre, and by the time the scholars move in, the muses for the most part have moved on. (Which is not at all to say that Davis and Mingus aren't great artists.)
There's also a great deal of ground that music theory formalizes that long-time musicians will grasp intuitively (but be less able to discuss, of course).
Just some complementary points.
If you want a comparison for music theory, try compiler theory (or just type theory).
Music theory is dead easy in comparison, no?