|
|
|
|
|
by gHosts
1726 days ago
|
|
Read actively. * If you have a working hypothesis as to what the code is doing, state that hypothesis as a comment. * If you think you know what it is doing, making that comment executable. ie. put in an assert. Better an assert punches you in the face than you rely on an incorrect analysis. * If you don't know WTF happening, or not sure, turn that comment into observability, add logging or something. * Make microcommits using rebase or the like, add observability, add asserts, add unit tests, add refactorings, make behavioural changes. * Do only one thing per commit, makes review and test much easier. |
|