{"id":926,"date":"2006-01-27T16:48:17","date_gmt":"2006-01-27T16:48:17","guid":{"rendered":"http:\/\/cleek.lunarpages.com\/blogs\/?p=926"},"modified":"2006-01-27T16:48:17","modified_gmt":"2006-01-27T16:48:17","slug":"minor-major","status":"publish","type":"post","link":"https:\/\/ok-cleek.com\/blogs\/?p=926","title":{"rendered":"Minor - Major"},"content":{"rendered":"

Like many bloggers, TBogg<\/a> does a weekly random Top 10. A lot of people (regulars, mostly) post their own random ten in response. We all get to feel good about ourselves, because everybody else has lousy taste in music - or something.<\/p>\n

Anyway, it looks like the majority of people who post their random 10 list them in \"Song - Artist\" order, instead of \"Artist - Song\" order. This annoys me (no big deal, I'm easily annoyed).<\/p>\n

It simply feels wrong to put the more-specific (and presumably less well-known) part of the song information before the less-specific (and presumably more well-known). You can assume everyone has heard of The Beatles. And you can assume not everyone has heard of their song \"Long Long Long\". <\/p>\n

Why does it matter? Well, for one thing, when I see a list of songs, I skim, looking for bands I like, dislike or merely recognize. If it's a band I dislike, I won't bother looking at the song title. Putting the band (the part of the info that people have a better chance of recognizing) first means people can evaluate the list, at least at one level, faster.<\/p>\n

Secondly, in all the programming languages I can think of, when you're looking at an object, or a structure, or any heirarchical data, you start with the most-general part, then work down to specifics, in a left to right order: MyObject.SomethingInsideMyObject.SomethingInsideThatThing.TheGoodies. Or, even more familiar, filenames: <\/p>\n