4 ms·
I explicitly said not to write “why” docs to explain specific value choices, but rather document the context around the setting, and what happens when the value
by TameAntelope 5y ago
I explicitly said not to write “why” docs to explain specific value choices, but rather document the context around the setting, and what happens when the value is raised or lowered, and why you might want to do that, so I’m thinking this isn’t a topic you’re grasping very well.
You’ll be fairly lonely if you reject working with everyone who’s read Clean Code, and truly alone if you won’t work with anyone who understands something better than you.
- hamburglar 5y agoAnd I explicitly said sometimes you want to write about the rationale. I didn’t actually realize you were attempting to dictate that that wasn’t allowed. That seems pretty nuts. And I think people who read Clean Code and aren’t dogmatic and condescending about trivial choices like this are pretty fine.
- TameAntelope 5y agoWhat you want and what is the best way to communicate are not always aligned. And I'm not dictating anything, or being dogmatic and condescending, but I guess it's easier to think I am if you're trying to have an Internet Argument Moment.
- hamburglar 5y ago> I'm not dictating anything, or being dogmatic You literally dictated that explanatory code docs shouldn’t talk about rationale for constants. And your evidence for this is that apparently Clean Code says so. > condescending Well you can claim not to be condescending all you want but that’s how I interpreted your explanation that the only reason I disagree is that you “understand it better,” and I’d imagine that’s how most people would read it.