Comment by polotics
4 hours ago
Let us try an experiment shall we: listen to any music you like and try and match the information the article provided to the complexity of what you are hearing. How much do you see a path from A(rticle) to S(ound in your ear).
This article is trivializing music down to a few not-so-important facts and mistaking some math for anything that would help `programmers` (?) understand music.
Maybe start by rewatching "This is Spinal Tap" instead, and consider that https://www.reddit.com/r/musictheory/comments/59n3pg/remembe...
> How much do you see a path from A(rticle) to S(ound in your ear).
Very clearly. The author constructed a melody from first principles in the article. You can take any song, deconstruct it using the information in there and begin to see why it sounds nice.
> This article is trivializing music down to a few not-so-important facts
This is a music theory lecture with code examples. Hardly “not-so-important”.
> mistaking some math for anything that would help `programmers` (?) understand music.
Compared to the lessons on https://www.musictheory.net this is definitely programmer/engineer friendly. It’s better than my old go-to at https://www.lightnote.co
Sure.
It is a trope amongst gigging musicians that over-intellectualizing the feels is a massive no-no.
Hence the joke about Db being the saddest chord... also Phil Collins said that, he would know :-D... ...and C# being the most evil chord. Hilarious.
I persist: "before you can be good, you first have to be bad" is more helpful music theory than that whole JavaScript visuals page.
[dead]