Software is a bit different from music or wine because taste can mean “has the right function and attention to detail and aesthetic and interface and data model and conforms to my expectations and has a certain kind of API and has documentation with actual examples and uses the right JavaScript framework and”, whereas taste in wine can mean “has a blend of flavors that I particularly like” and taste in music can mean “pushes the boundaries of its genre and introduces genuinely new sounds”. Most but not all of what we want out of software is about function and utility and intuitive UX.
But wine and music and other subjective consumption-hobbies that enable snobbery are much less grounded in practicality and tend to become arenas for novelty/pure experimentation (charitably) or countersignaling and identity-building (uncharitably). So you end up with situations where the people who “have good taste” consistently associate themselves with music that sounds legitimately bad to regular listeners or never gets popular enough to be recognizable because it’s about being better than casual music listeners more than it is about the music to them. Or, proclaiming that no taste preferences for icecream products are worthy of respect unless they come from someone that regularly consumes pistachio ice cream - it’s not about the ice cream to them.
That’s why we can say “this UI needs to be collapsible and expanded by default” about software - we want it to be a certain way. The type of people who relish in their taste in music and ice cream don’t tend to say things like “maybe cut the bridge 10 seconds and add some kind of duet with reverb” or “it used too much nitrate fertilizer for loamy soil and ended up kind of woody (for ice cream)” because they want themselves to be a certain way.
I don’t dispute that. What I’m saying is that functional and even non-functional taste in software tends to be grounded in how it can more effectively serve our needs. In a way that’s actually a more profound kind of creativity and taste than something that tries to just look cool.
OTOH music and anything else snob-adjacent aren’t grounded in serving our direct needs to some other end the same way software tends to be, so to them “taste” could be reducible to just a favorite flavor or becomes a kind of status/value/oneupmanship. The products are consumed directly as ends unto themselves so people who have strong opinions on their comparative tastefulness care about that for different reasons than they do software.
But wine and music and other subjective consumption-hobbies that enable snobbery are much less grounded in practicality and tend to become arenas for novelty/pure experimentation (charitably) or countersignaling and identity-building (uncharitably). So you end up with situations where the people who “have good taste” consistently associate themselves with music that sounds legitimately bad to regular listeners or never gets popular enough to be recognizable because it’s about being better than casual music listeners more than it is about the music to them. Or, proclaiming that no taste preferences for icecream products are worthy of respect unless they come from someone that regularly consumes pistachio ice cream - it’s not about the ice cream to them.
That’s why we can say “this UI needs to be collapsible and expanded by default” about software - we want it to be a certain way. The type of people who relish in their taste in music and ice cream don’t tend to say things like “maybe cut the bridge 10 seconds and add some kind of duet with reverb” or “it used too much nitrate fertilizer for loamy soil and ended up kind of woody (for ice cream)” because they want themselves to be a certain way.