Comments on: Some ideas on making sure done is really done

by: Daniel Jimenez

Thu, 28 Jun 2007 16:14:13 +0000

There were supposed to be tabs:

W20070627
morningCheckoutAndBuild:0900:0930
currentRelease:0930
..particularTask:0931
….ClassBeingWorked:0932:1021
……testOneThing:0932:0937
……testAnother:0938:1020
….push-meeting:1030:1105
….NewClass:1110
……create:1110:1115
……testNewStuff:1115…

by: Daniel Jimenez

Wed, 27 Jun 2007 19:00:06 +0000

I keep a timings file. Each date gets a heading, then the tasks I perform are listed with timestamps showing start and finish.

For example (with slight fudging):

W20070627
morningCheckoutAndBuild:0900:0930
currentRelease:0930
particularTask:0931
ClassBeingWorked:0932:1021
testOneThing:0932:0937
testAnother:0938:1020
push-meeting:1030:1105
NewClass:1110
create:1110:1115
testNewStuff:1115…

At the bottom of the file I keep a list of todo`s.

I started this when I started TDD: whenever I started a new test, I’d put the test name and a timestamp in the timings file, then when the code was checked in I’d put an ending timestamp on it.

Of course, the file has since grown to document more of my development activities than just tests now.

by: Ryan Cooper

Mon, 25 Jun 2007 20:38:42 +0000

Hi Alex;

Thanks for your thoughts. I particularly like the diff review before committing code. It’s a really beneficial practice, but one I occasionally find myself slipping away from. Thanks for the reminder!