5,125 reputation
11330
bio website
location Manchester, United Kingdom
age 32
visits member for 2 years, 6 months
seen Jul 23 at 21:50

May
18
awarded  Nice Answer
Jan
31
awarded  Yearling
Jan
30
awarded  Good Answer
Oct
22
comment Presenting agile estimates for Pivotal Tracker project
I'm a bit suspicious of those "complexity" values. They look like story points, but 1-4 seems like a very limited range.
Oct
21
comment Why do we use story points instead of man days when estimating user stories?
Further re. point 2: User stories are developed by the team, not individual developers. It's the team's work-rate which is the important part. Bear in mind that when implementing user stories you should be breaking them down into tasks first. Give the faster developer more tasks!
Oct
21
comment Why do we use story points instead of man days when estimating user stories?
Re. point 1: For my money, if you're talking about 2 different sets of tech and 2 different areas of the product, you've got two teams.
Oct
21
comment Why do we use story points instead of man days when estimating user stories?
@Giorgio Re. point 2: Your faster programmer has a work rate of 1 story point/day, and your slower programmer has a work rate of 0.5 story points/day. If you do it in hours, either your faster programmer is going to work himself to death, or your slower programmer needs sacking. Bill Leeper's answer makes this point very well.
Oct
21
answered Is implementing an interface defined in a subpackage an anti-pattern?
Oct
17
comment Empty interface to combine multiple interfaces
I can't think of a time when I've needed a single stream which is both readable & writeable, and judging from other people's answers/comments I don't think I'm the only one. I'm just saying it might be more helpful to choose a less controversial pair of interfaces...
Oct
17
comment Empty interface to combine multiple interfaces
This is a good question, but I think using Readable and 'Writable' as your example interfaces is muddying the waters somewhat since they are usually different roles...
Oct
11
comment Should there be a formal role (internal or external) assigned to dev environments to control wasteful complexity?
I'm not sure you could justify a position for someone who could be replaced by a piece of paper with "YAGNI" printed on it. ;)
Oct
10
comment Choosing the right resources
I realise this is stating the obvious, but what about reading reviews?
Sep
12
comment Why would I ever use delegates if I'm not doing events?
It isn't specific to delegates or even C#, but Joel S gives a really good case for functional programming here: joelonsoftware.com/items/2006/08/01.html
Aug
30
answered Is there a name for the concept of a “cumulative checksum”?
Aug
29
revised Does Scrum make sense when implementing a new compiler backend?
added 98 characters in body
Aug
29
comment Does Scrum make sense when implementing a new compiler backend?
@JeffO If you want to nitpick, requirements do not always change, they almost always do. I'll change my wording regardless.
Aug
28
awarded  Nice Answer
Aug
28
answered Does Scrum make sense when implementing a new compiler backend?
Aug
22
comment Breaking down a complex story at project start
The user story is done when all the tasks required to fulfil it are complete. If you end up splitting a story across a couple of sprints it might throw off the velocity a little for those particular sprints, but it comes out in the wash and your average should still be useful.
Aug
22
comment Breaking down a complex story at project start
Breaking up work into tasks which are at most 1-2 days' work is definitely a good idea, and a lot of people would say it's essential. However, tasks != user stories. Tasks are the discrete bits of development you need to do in order to fulfil user stories, and a single user story may comprise many tasks.