Hacker News new | past | comments | ask | show | jobs | submit login

I find writing commit messages helps my development flow:

Why did I spend an hour refactoring 1000 lines of rust code again?

It worked the first time I got it to compile again, so it's probably fine, but it was a subtle non-functional change. I'd better commit + write a good message so:

- I don't forget why I just did that

- In case I need to back out the next step

- So that my coworkers know what I'm up to, and don't ask me on slack.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: