Comments for Joakim Karlsson

Comment on Goal-Oriented Daily Stand-Ups by Joakim

Joakim — Sat, 13 Feb 2010 12:53:33 +0000

For a team where the members are working on too many things at once, where we find that most stories are finished at the end of the iteration instead of experiencing a constant flow of finished features, we might set a goal for ourselves that “the application should be able to do X by tomorrow”.

A team might also set goals regarding its working agreements, such as “by tomorrow we should have switched pairs at least x times”.

Comment on Goal-Oriented Daily Stand-Ups by sn

sn — Sat, 13 Feb 2010 04:33:19 +0000

can you give an example of a goal?
thanks

Comment on The Locality of Code Changes by Dazed & Confused » The cost and benefits of cleaning up code

Dazed & Confused » The cost and benefits of cleaning up code — Tue, 10 Nov 2009 14:57:59 +0000

[...] though it is not very scientifically conclusive Joakim Karlsson has some very interesting results on the locality of code changes. As Joakim discusses this relates closely to how you evaluate wether the code you are currently [...]

Comment on The Locality of Code Changes by Weekend miscellany — The Endeavour

Weekend miscellany — The Endeavour — Sat, 04 Jul 2009 12:18:03 +0000

[...] Karlsson says in his post The Locality of Code Changes “The probability that you will change a piece of code in the near future increases when you [...]

Comment on The Locality of Code Changes by Joakim

Joakim — Sat, 04 Jul 2009 07:24:12 +0000

Yes, I think I see your point. My data just shows that there is a distribution of waiting times between changes to code, but it fails to show anything about whether changes to dormant files really lead to a higher frequency of revisits. Right?

Comment on The Locality of Code Changes by Brandon Moore

Brandon Moore — Fri, 03 Jul 2009 22:59:44 +0000

I don’t think that histogram is very conclusive. You get an exponential falloff if you plot a histogram of waiting times between events from a Poisson process. A scatter plot comparing successive commit intervals might show the correlation you are looking for.

Comment on The Locality of Code Changes by Chris Sterling

Chris Sterling — Wed, 01 Jul 2009 23:57:12 +0000

Great information! Thank you for the research that you did and there seems to be something to the results you found.

Comment on The Locality of Code Changes by Joakim

Joakim — Wed, 01 Jul 2009 19:51:35 +0000

@Brett, @Stefano:

Interesting tip. Thanks.

I also wonder if there is a way to display the distribution between what files ends up where in the histogram. Are we just seeing the same few files being changed over and over again, or is there a more interesting distribution?

Comment on The Locality of Code Changes by Joakim

Joakim — Wed, 01 Jul 2009 19:33:13 +0000

@MSR:

Wow! I never heard of MSR before. Thanks for the info.

Are there any specific articles or other materials about this that you could point me at?

Comment on The Locality of Code Changes by MSR

MSR — Wed, 01 Jul 2009 18:54:42 +0000

This kind of behaviour has been observed and described repeatedly at conferences like Mining Software Repositories, International Conference of Program Comprehension, PROMISE, ICSE, ICSM, etc.

Co-change is also observed. If you change two files together in the past, you will probably change those two files again in the future.