[B3A]

Writing comments for the future.
Like diary notes, because if I did something, I need to know everything I was thinking at that moment. It saved me hours of "what was I thinking"

[xadamxk]

Commit messages that actually mean something.
Bonus points for adding additional context in the commit description

[Dystortion]

Writing comments for the future.
Like diary notes, because if I did something, I need to know everything I was thinking at that moment. It saved me hours of "what was I thinking"

My notes are overly descriptive at times when I'm the only one reading it and I know what's happening at a glance but sure let me write an essay for this. But to add to that, commenting throughout can an insane tool - comment first then write imo. See writing code then commenting, you're usually just giving a quick explanation for what you've just wrote but actually stating "gonna put x before to interact with xyz/y.go in doing z job - implementation I'm thinking is ..." It helps give me structure and ideas. I might be crazy though

[Dirty]

Once every blue moon I like to rawdog an issue I'm working on by not using anything outside of the codebases infront of me. No documentation and no internet, just go to definition and diving into the rabbithole.

I think often especially in the webdev world people have gotten too used to rely on other people to figure their shit out, so when they are the first to do something (i.e in internal tools) they are completely lost.