http://agilepainrelief.com/notesfromatooluser/2008/05/mythbusting-c.html?utm_source=rss&utm_medium=rss&utm_campaign=mythbusting-c Best practices for your goals Sat, 19 May 2012 03:39:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://agilepainrelief.com/notesfromatooluser/2008/05/mythbusting-c.html/comment-page-1#comment-177 Steve Campbell Tue, 30 Nov 1999 00:00:00 +0000 http://agilepainrelief.com/2008/05/mythbusting-c/#comment-177 Since we're busting myths, I will say that it is *not* necessary to practice pair-programming to achieve collective code ownership. We managed just fine without that - all that was necessary was that multiple people simultaneously worked on the same areas of functionality. Since we’re busting myths, I will say that it is *not* necessary to practice pair-programming to achieve collective code ownership. We managed just fine without that – all that was necessary was that multiple people simultaneously worked on the same areas of functionality.

]]> http://agilepainrelief.com/notesfromatooluser/2008/05/mythbusting-c.html/comment-page-1#comment-178 Mark Levison Tue, 30 Nov 1999 00:00:00 +0000 http://agilepainrelief.com/2008/05/mythbusting-c/#comment-178 Steve - hoisted on my own petard. I should have said that in my limited experience in enviroments that pair programming isn't used I've found that we've had trouble with CCO. If you've been able to pull it off then well done and you have a good counter point. Steve – hoisted on my own petard. I should have said that in my limited experience in enviroments that pair programming isn’t used I’ve found that we’ve had trouble with CCO. If you’ve been able to pull it off then well done and you have a good counter point.

]]> http://agilepainrelief.com/notesfromatooluser/2008/05/mythbusting-c.html/comment-page-1#comment-179 Ilja Preuß Tue, 30 Nov 1999 00:00:00 +0000 http://agilepainrelief.com/2008/05/mythbusting-c/#comment-179 I'd also like to add that CCO does *not* mean that I have to be able to work equally well on every line of code in a one million LOC project. It means that when I see code that needs improvement, "it's not *my* code" is not a valid excuse to leave it as is. I’d also like to add that CCO does *not* mean that I have to be able to work equally well on every line of code in a one million LOC project. It means that when I see code that needs improvement, “it’s not *my* code” is not a valid excuse to leave it as is.

]]>