4,323 karma · joined September 27, 2021
That’s interesting. Is the documentation in the project management system? What tool is that?
Uh huh. The comment that you replied to is pretty much in line with the wider “patch does X to the code” which isn’t about anthropomorphizing. That’s the spin that you put on it.
It’s about as much anthrop. as saying that a falling piano crushed someone’s leg.
> We do it for usability and other reasons and one only needs to look at git itself to recognize that the original authors did not have usability in mind when designing it. What they built is incredibly powerful, but it's rare for usability and technical prowess to overlap.
It’s also rare to find commit message quality that is on the level of the regular contributors to that project. Which has nothing to do with how unfortunate the UX of the tool is.
It’s not like you need the history (is this a refactor or something else? doesn’t matter) so you don’t need to keep around such failed attempts.
But that’s the whole point of a version control system. That’s all it is for.
If that is super impractical then our VCSs (Git and others) must be too impractical to use.
It’s a version control system. That includes an explanation as well. The explanation for each revision is integral.
And I don’t think people here really disagree with that. Just that they might prefer to put all that integral information somewhere else—the information (princess) is in another castle, Mario. Why? Why not at least just copy-paste the relevant information into the version control system proper? I see this all the time; people often do the same with GitHub pull requests—paragraphs upon paragraphs in the pull request description and then just a “Merge <convoluted URL>” in the merge commit message!
It’s not that I blame people for this. Maybe Git is just so unergonomic that many would prefer to offload everything into another interface (even Jira).
[1] My tickets will usually have all the history. Maybe a lot of back and forth. The commit message though will just have what was done when all was said and done—no back and forth, just the result. And some of my tickets probably don’t even have a description body since what I ended up doing is just described in the commit message.
Refactor x
As in: command (verb: refactor) the code to change in this way. That a person wrote the code is irrelevant.There’s your answer.
Yeah.
[1] Except some light scripting
When people see stereotypes or “types”, the point is never—unless they are genuinely denigrating them—that they are completely alien or that whatever institution they belong to is not “made up of humans”.