Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

When developing something new, I make tons of tiny work-in-progress commits, sometimes dozens in a day, and frequently go back and squash them with rebase into a logical flow of changes, once it's more clear what that logical flow really is. I keep my WIP branches around locally for a while so I can go back and dig out the experiments I made along the way.

I prefer this over trying to get every commit right the first time. I also feel there's a nice change of pace in the process of stepping back, looking over the previous work, and shaping it into something that communicates the ideas well to reviewers.



What is the purpose of committing though? What does it additionally get you that you don't get by working in place without committing?




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

Search: