3 ms·
When I first read the article's title, I thought basically the same thing: this is about the concepts the programmers embrace. But it turns out to be about the
by HillaryBriss 11y ago
When I first read the article's title, I thought basically the same thing: this is about the concepts the programmers embrace. But it turns out to be about the concepts the end users must embrace.
It's unclear to me how those two things are related. They _can_ be related, but it doesn't seem like they have to be. Not sure.
- andy_wrote 11y agoI think they don't have to be related. The article's example of tags and folders is a good illustration. "Tag" and "folder" models might have a clear enough implementation in the code; a programmer might wonder why they're both implemented but may have no trouble supporting both in principle. But the existence of both may be very confusing to the user. The cost inflicted on the coders is not coders' conceptual debt, but users's conceptual debt - certainly costly to coders as they have to support multiple patterns, but I think there is a difference. I guess when I think of coders' conceptual debt, I'd think of something that may be abstracted away at the UX level such that the user doesn't see it, but inflicts pain on implementors due to counter-intuitive patterns.