4 ms·
One solution to the OP's problem is to continuously document the activity leading up to those two lines of code. That way you can point to the notes and say "he
by sriku 6y ago
One solution to the OP's problem is to continuously document the activity leading up to those two lines of code. That way you can point to the notes and say "here's why" .. and I've found that quite often justifiable and shows you've not been goofing off. Furthermore, it also helps someone who'll have to look at those two lines later on to grab some context and understand why they're there.
This could be as simple as notes logged against an issue about experiments done, etc.
- franky47 6y agoAlso, adding this log to the commit message itself, to preserve context for future developers reaching that code. Duplication might be necessary for discovery depending on the tools used. https://dhwthompson.com/2019/my-favourite-git-commit https://dhwthompson.com/2019/my-favourite-git-commit
- sriku 6y agoSome fun folklore involving Bill Atkinson at Apple - logging "-2000" lines of code written. https://www.folklore.org/StoryView.py?story=Negative_2000_Lines_Of_Code.txt https://www.folklore.org/StoryView.py?story=Negative_2000_Li...