@J12t Documenting inside the coding prior to touching the code, with (uncommitted) tasks and opinons inside it.
It provides more of a historical overview of the coding as it (eventually) changes, as well as reminds oneself and others of the forgotten facets; justifications; and functionalities.
Otherwise starting with a blank file, which has a strong delineation:
Do I copy the entirety of the function?
Does this function need adapting?
It forces the hand across the ecosystem esp wrt cruft