I believe I’m abiding by the definition inherent to his sequence, but anyone is free to convince me otherwise.
(Please also let me know if I’ve violated some norm about naming conventions.)
I’ve decided to use “«boundaries»” instead of “boundaries” because “boundaries” colloquially refers to something that’s more like “Hey you crossed my boundaries, you’re so mean!” (see this post for examples), and while I think that these two concepts are related, I find them extraordinarily confusing to consider simultaneously (because “crossing ‘boundaries’” does not imply “crossing «boundaries»”), so I try to be explicit as possible with the use.
In the future I plan to use that word as little as possible because of this, but unfortunately that’s the name of the sequence.
LW is somewhat opinionated about how to do tags. (This doesn’t mean there’s a hard-and-fast-rule, just that when we’re evaluating what makes good tags and considering whether to re-organize tags, the mods reflect on the entire experience of the LW userbase). Generally, we want tags that are “neither too narrow nor too broad”.
In this case, if there were other people writing about boundaries-in-a-technical-sense which for some reason was notably different from Critch’s definition, and there were some people (maybe just Critch, maybe Critch-plus-a-few-collaborators) who specifically wanted to focus on his definition, then having two tags would make sense. By guess is that anyone writing about boundaries-in-a-technical-sense would end up with a definition similar to Critch’s, and there should be just be one tag for all similar work, and the ‘«’ symbol doesn’t make sense for the tag.
Ok, I will rename the tag from “«Boundaries»” to “Boundaries [technical]”. Fwiw I consider both strings as referring to the same concept, but I see how it might be weird to use «».
I believe I’m abiding by the definition inherent to his sequence, but anyone is free to convince me otherwise.
(Please also let me know if I’ve violated some norm about naming conventions.)
I’ve decided to use “«boundaries»” instead of “boundaries” because “boundaries” colloquially refers to something that’s more like “Hey you crossed my boundaries, you’re so mean!” (see this post for examples), and while I think that these two concepts are related, I find them extraordinarily confusing to consider simultaneously (because “crossing ‘boundaries’” does not imply “crossing «boundaries»”), so I try to be explicit as possible with the use.
In the future I plan to use that word as little as possible because of this, but unfortunately that’s the name of the sequence.
But “Boundaries [technical]” could do…
LW is somewhat opinionated about how to do tags. (This doesn’t mean there’s a hard-and-fast-rule, just that when we’re evaluating what makes good tags and considering whether to re-organize tags, the mods reflect on the entire experience of the LW userbase). Generally, we want tags that are “neither too narrow nor too broad”.
In this case, if there were other people writing about boundaries-in-a-technical-sense which for some reason was notably different from Critch’s definition, and there were some people (maybe just Critch, maybe Critch-plus-a-few-collaborators) who specifically wanted to focus on his definition, then having two tags would make sense. By guess is that anyone writing about boundaries-in-a-technical-sense would end up with a definition similar to Critch’s, and there should be just be one tag for all similar work, and the ‘«’ symbol doesn’t make sense for the tag.
Ok, I will rename the tag from “«Boundaries»” to “Boundaries [technical]”. Fwiw I consider both strings as referring to the same concept, but I see how it might be weird to use «».