2 ms·
The idea is for junior to learn from massive commit that affected many files?
by watwut 3y ago
The idea is for junior to learn from massive commit that affected many files?
- mixmastamyk 3y agoThis 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 months later, e.g. where I move code needed multiple times into a more central mixin location.