People always think you write documentation for other people who read your code. This is false, because you're going to be assigned the bug anyway when they see it's your code on git.
You're writing documentation as a favor to future you. He's going to re-read that in about a month and be like "wtf was I thinking?"
It's like doing the dishes. You're not doing it because you need dishes now. You're doing it so that when you do need dishes, you won't have a pile of dirty dishes starting at you until you give up and eat over a napkin.
Ah, who am I kidding. You're still not gonna write docs.
demon_ix on July 3rd, 2018 at 11:10 UTC »
People always think you write documentation for other people who read your code. This is false, because you're going to be assigned the bug anyway when they see it's your code on git.
You're writing documentation as a favor to future you. He's going to re-read that in about a month and be like "wtf was I thinking?"
It's like doing the dishes. You're not doing it because you need dishes now. You're doing it so that when you do need dishes, you won't have a pile of dirty dishes starting at you until you give up and eat over a napkin.
Ah, who am I kidding. You're still not gonna write docs.
siryaXI on July 3rd, 2018 at 11:24 UTC »
If only we could do a save state of our mind to reload later
Mperonen on July 3rd, 2018 at 12:34 UTC »
Just comment out the whole code you've been working on so it's self-explonary on monday.