Re:Julia Evans: Git rebase, what can go wrong
by deredede on Tuesday November 07, 2023 @01:40AM
(#38173908)
A commit is not a method, it is a change set potentially affecting many files. Pointing people to the commit used to implement feature A lets them understand the whole story of which components need to change (and how) to implement similar feature B in a way that pointing them to a single method or file doesn't necessarily can.
[ Parent
| on HN ]
Re:Julia Evans: Git rebase, what can go wrong
by watwut on Tuesday November 07, 2023 @05:07PM
(#38183655)
The idea is for junior to learn from massive commit that affected many files?
Re:Julia Evans: Git rebase, what can go wrong
by mixmastamyk on Tuesday November 07, 2023 @06:13PM
(#38184422)
This reply is overstating a bit, but it does sound like a lot of work simply to avoid saying, "here look at these methods in this file" and the unstated, and trace the imports yourself.
Not to mention just finding the right commit months later sounds like more work than that already.
Personally, even if I were to make the history absolutely perfect, I never get the code right (interfaces etc), the first time. It might be hours or days before I'm 98% happy with the final implementation. Sometimes big refactor opportunities come to me days or months later, e.g. where I move code needed multiple times into a more central mixin location.