tag:blogger.com,1999:blog-3258074296776382669.post8261532267423894926..comments2022-12-03T08:51:36.571+01:00Comments on A World Full of Sharp Objects: Commit-Driven DevelopmentKjetil Klaussenhttp://www.blogger.com/profile/15985372289245420671noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-3258074296776382669.post-76211782855791340862012-10-22T12:31:33.521+02:002012-10-22T12:31:33.521+02:00@YvesHanoulle - We're using Subversion and Vis...@YvesHanoulle - We're using Subversion and Visual Studio. I'm using the AnkhSVN plugin for VS (http://ankhsvn.open.collab.net/), and in the 'pending changes' window I use enter the comment for my next commit when I start working on something. If I discover more things I should do or new things come up, I either do a commit with a "WIP:..." (Work In Progress) and then switch over, or if it's a quick fix that only span a file or two I'll commit those files separately and continue on my original work. If the new work item can wait, I just jot down the commit comment for that on paper and then enter that one in 'pending changes' as soon as I've committed what I was working on.Kjetil Klaussenhttps://www.blogger.com/profile/15985372289245420671noreply@blogger.comtag:blogger.com,1999:blog-3258074296776382669.post-4099872964874608202012-10-22T11:50:14.151+02:002012-10-22T11:50:14.151+02:00I'm confused in how you do this. what tool do ...I'm confused in how you do this. what tool do you have that allows you to do this?<br />or do you write it in your favorite editor and then after writing the copde copy paste it?<br /><br />YvesHanoullehttp://www.hanoulle.benoreply@blogger.comtag:blogger.com,1999:blog-3258074296776382669.post-6095418051206036742012-10-19T07:46:05.787+02:002012-10-19T07:46:05.787+02:00@Rainsberger - Exactly! I think about the commit i...@Rainsberger - Exactly! I think about the commit in the same way; What's the new features of the system. And I try to think about it in the context of the end user; If my comment would end up in the release notes, would it make sense to the customer?<br /><br />@Hurst - Yeah, I have the same problem my self. Starting out implementing a new feature and then discover some smaller and bigger refactorings that I should have done on the way. But I find that writing that comment first makes it easier to focus on what I started out with. If I discover other things along the way, I make a note (on paper) and then see if I can tackle that in the next commit. For smaller refactorings I just do them along the way.Kjetil Klaussenhttps://www.blogger.com/profile/15985372289245420671noreply@blogger.comtag:blogger.com,1999:blog-3258074296776382669.post-70204770552951381572012-10-19T07:42:13.504+02:002012-10-19T07:42:13.504+02:00My way of looking at it is, if I go to do a blame ...My way of looking at it is, if I go to do a blame on this line a few years from now, is there enough context to know what happened.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3258074296776382669.post-31734277576495342012-10-19T04:23:17.821+02:002012-10-19T04:23:17.821+02:00A problem I have (and it's one that commit-dri...A problem I have (and it's one that commit-driven development may help solve) is that I have a goal in mind at the onset of my plunge, but by the end, I've made more changes than I had anticipated and there's no good way to break up the commit. Taking the time to mentally break apart the commit at the front end could only help me.Josh Hursthttps://www.blogger.com/profile/07993730212970126190noreply@blogger.comtag:blogger.com,1999:blog-3258074296776382669.post-78683115652310718112012-10-18T18:57:34.109+02:002012-10-18T18:57:34.109+02:00Whenever I write a commit comment, I like it to an...Whenever I write a commit comment, I like it to answer the question, "What can the system now do that it couldn't do before?" If I can name more than one significant thing, then it's possible I've committed too much, and try to take smaller steps.<br />J. B. Rainsbergerhttps://www.blogger.com/profile/16213943899864372362noreply@blogger.com