JESSICA RUAN

We Making Music Now?!

Moosic

How I Moosic

  1. Motif! A motif is a short musical idea that is meant to recur throughout your piece. "Motif" sounds fancy and profound, but in literal terms it's a small phrase of notes that you can hum in a couple of seconds. Starting out, I suggest simple motifs, and just ONE per piece.
  2. Next... chords. Throw some chords underneath your motif and see what sounds good.
  3. Ctrl+C Ctrl+V your motif on top of your chords, over and over. For some chords, your motif won't quite fit as-is. When this happens, you shift the motif up or down a few pitches, or tweak a few notes within the motif, until it sounds nicely at home on top of those chords.

There's a lot of music theory behind steps 2-3, where certain chords conventionally lead into certain other chords, and certain chords evoke certain emotions. I'm happy to talk about these in a future post!

On Moosic Theory and Chord Progression Mush

For me, it helps to not think about music theory too much. See, I'm a huge fan of video essays that talk about chord progressions and why some chord progressions sound good, yknow, the ones with the catchy titles like "that ONE WEIRD TRICK that makes your favorite song give you goosebumps, and guess what?? the secret sauce is the CHORD PROGRESSION!!!"

As an amateur composer, these videos naturally gave me the impression that the chord progression was the most important thing, so obviously I had to start there. And not just any chord progression; it had to be the most distinct, most emotionally devastating progression I could come up with, or else my melody would be missing this goosebump-inducing "secret sauce".

After arriving at such a chord progression, only then did I permit myself to build a melody on top of it, note by note, by only picking notes that were "legal" for each chord. Boom, music!

My chord-first music sounded bad, because it would either not have a motif at all, or the motif would sound bad.

The best way I can describe this is that it's like writing an essay by starting with a five-paragraph outline of arbitrary, vibes-based topics that each sound cool on their own...

"okay, paragraph 1 is about dogs, paragraph 2 is about the French Revolution, paragraph 3 is about photosynthesis, why not?"

...and then dutifully filling in each paragraph with grammatically correct, perfectly on-topic sentences. Boom, essay!

Yes, outlines are supposed to give your ideas structure, and yes, they map out the emotional arc of a piece. Plenty of people love taking a great essay and breaking it down into its outline to show why it works. But if you're coming in without a central point, without some idea of ONE thing you want your reader to remember, you have yourself some neatly organized mush.

Now I start with the motif, and I work out the chords and everything else afterwards to support it. I do still delight myself with theory and I consult theory when I can't decide between two chords that both sound fine, but I use it more as a tiebreaker than a guiding principle.

_Why We Making Moosic Now?

I've had the thought, "I want to compose music" cross my head a few times and gave it a shot sporadically over the years.

The thing that made me truly commit to learning music composition was finding Why's (poignant) Guide to Ruby, by the programmer why the lucky stiff, sometime in 2024. It was the first programming book I'd ever found that came with its own soundtrack.

(I'll be honest, I think the book's tangents make it a little hard to follow, but it's easily the most memorable piece of Ruby teaching material out there. For a lot of people it was the gateway that got them into Ruby, and from there into programming more seriously.)

Anyway, one of my dreams at that point was (and is) to write a programming book and publish it on the web, sort of like what Bob Nystrom did with Crafting Interpreters and Game Programming Patterns, so _why's book really rearranged my plans for it. It was weird in a way that stretched my idea of what a programming book can be.

I should learn to compose music for realsies, because how cool would it be if my web book had its own soundtrack?

"if you program and want any longevity to your work, make a game. all else recycles, but people rewrite architectures to keep games alive."

...was one of _why's last tweets before he deleted his entire online presence in 2009. He'd built some of Ruby's best-loved libraries and frameworks, but he'd grown disillusioned.

The way I personally interpret this, a lot of industry work has a short shelf life. Software is often replaced by better and newer software, and some years after that, it won't even run, unless someone is insane enough to dig it up and rebuild the whole world it used to run on just to resurrect it.

Games are uniquely likely to rack up a cult following of these insane people. People port Doom to places it has no business running, and people have built emulators and archives to rescue thousands of little games so that you can still play them today, and they do it because they are insane and because they love those games too much to let them die.

Now, I don't know whether the internet's gotten dead and boring, or I've gotten dead and boring, so let's call the intersection of these two "my internet."

Whatever happened to just stumbling onto a weird flash game or a serial novella or a CYOA that strangers debate over in forums? Then it hit me that I'm now roughly the age most of those creators were when they made the stuff I loved.

So, the web book I dream of writing might still end up being a serious programming book, but fiction and games are on the table now too.

Future

The first draft of this post was longer! I shortened it a lot; I deleted my opining about some tricks I use to pick motifs, plus thoughts on math rock and on jazz vs. classical and that you'll be hearing math rock from me pretty soon.

I also cut a whole tangent about how I’m classically trained in piano, and composing has made it pretty clear how much I don’t know. As you may know, classical music heavily rewards students who are meticulous about playing things just right, and I was a "close enough" kind of classical student, and of course I got narrated 《差不多先生传》 ("Biography of Mr. Close Enough"), whose 差不多-ism ends with him dying, due to letting a cattle doctor treat him because the name of the cattle doctor was close enough to the real doctor’s. My 差不多-ism, on the other hand, was thankfully less fatal, and I managed to drag my way through RCM Level 10 but not without feeling like I left something unfinished.

I wonder if I would’ve been more motivated about music back then if lessons also made room for composing my own stuff and improvising in non-classical genres.

But c'mon, I've only just started composing and I've only put out one song on Bandcamp!

Before I write about music, I should... put out a little more music first?