The letters and flats/sharps give you key/value over frequencies, which is better than just a numeric index over a chromatic scale. Working with the keys allows for the same abstractions to be used with all 12 keys at the same time, on the same staff.
You can almost guess what instrument the composer played because of that bias. If you see a violin piece with 6 flats, it's a pretty good guess that the composer didn't play violin.
I'm being ripped off too. graduated during the recession after the dotcom bubble, took the first dead-end dev job I could find, not exactly marketable experience.
D-E-F by itself would probably be considered a D minor triad with a 9, and the missing 5th is implied (the 5th would exist as an overtone for most instruments too). that's kind of a stretch though.
For the generation part, it might be a good idea to separate "music" into its parts (like bass, drums, melody, chord-rhythm, chord-ambient-background, and other stuff like secondary melodies, horn section arrangements or whatever). A unique model for each one of those could learn differently. Each of those parts could be broken down even further too.
Basically yeah. An object can have one delegate object, which implements a set of required and optional methods defined in a protocol. So the delegate can add customized behavior to an object without subclassing.
Don't they need to redesign all the climate models now that gravitational waves exist? A giant wave would make the sun closer to the earth and thus global warming.