undefined | Better HN

0 pointsakkartik13y ago0 comments

I prefer to record design decisions not inline in code comments but in my git commit log. Design decisions are best viewed as a chronological big-picture conversation with myself as I try out different things. I also find them to be just concise enough.

I don't use it anymore, but this was how I got started on this approach: http://akkartik.name/codelog.html

0 comments

blu3jack13y ago

Thanks for the link, that's pretty interesting. Do you use a modification of this now, or have you simply codified that approach internally and commit intuitively?

akkartikOP13y ago

Yeah now it just goes into the commit log. The 'training wheels' were useful to get myself committing more frequently.

Here's a kinda-random sample from my current obsession: http://github.com/akkartik/wart/compare/587e30dc51...8da3d3c...

blu3jack13y ago

Seems ok. Not sure it's the "answer" to making sense of a codebase, but it's certainly addresses part of the problem. Why do you number your files, e.g. 003parse.cc?

1 more reply

j / k navigate · click thread line to collapse

0 pointsakkartik13y ago0 comments

I don't use it anymore, but this was how I got started on this approach: http://akkartik.name/codelog.html

0 comments

blu3jack13y ago

Thanks for the link, that's pretty interesting. Do you use a modification of this now, or have you simply codified that approach internally and commit intuitively?

akkartikOP13y ago

Yeah now it just goes into the commit log. The 'training wheels' were useful to get myself committing more frequently.

Here's a kinda-random sample from my current obsession: http://github.com/akkartik/wart/compare/587e30dc51...8da3d3c...

blu3jack13y ago

Seems ok. Not sure it's the "answer" to making sense of a codebase, but it's certainly addresses part of the problem. Why do you number your files, e.g. 003parse.cc?

1 more reply

j / k navigate · click thread line to collapse