clickheat Extreme Programming Club: XP Practices: Refactorig, branching and merging. Joys and Pains.

The Yorkshire Extreme Programming and Agile Methods Club

The Extreme Programming Club has changed it's name Please visit for details. All postings for upcoming meetings will now be made there.

Where we meet:
Our meetings are held on every second Wednesday of each month at Victoria Hotel Pub in Leeds city centre at 7.00pm.
Place »
Directions »
Google Callendar »
Join our mailing list for updates and interesting discussion on technology, project management, programming and many more...


XP Practices: Refactorig, branching and merging. Joys and Pains.

At our next meeting (on the 9th of July at 7pm, in Victoria Hotel Pub) we are going to have a moderated debate about various specific eXtreme Programming practices, like refactoring, branching, merging, and possibly more...

If you have any views on those or you have no views at all but would like to hear, what IT practitioners think of those, please come along.

We'll do our best to provide you with a drink and a snack.


Blogger Jonathan said...

It was a really good session. Lots of lively debate with what seemed to be a decent conclusion. I liked being asked "what have you learned tonight?" at the end of the evening.

I've been making plenty of notes and will try to provide you all with a write-up by tomorrow.

10 July 2008 at 08:38

Blogger NeilM said...

Couldn't agree more - learned lots and pleased with the ebb and flow of the discussion. David T mentioned a book on legacy systems - anyone remember what it was called? Cheers Neil

10 July 2008 at 22:57

Blogger Daniel Drozdzewski said...

I have arrived late, but have seen your round-up and it seems that the discussion went really well.

I personally (being obsessed about the control loops) think and could see in all your answers, that good processes were ALWAYS about tightening up the control loops. Ideas like 'zero bugs' is the loop reduced virtually to nothing or to few synapses looped in the brain of a developer, instead of following loop code - commit - continuous_integrate_it - fix, which is much bigger and time consuming.

Also it feels that only overhead in using 'zero bugs' policy is initial transition and reaching the status of zero bugs. However aiming for no bugs and doing daily coding must gradually shift people between horribly world of bugs and pain to a pink and jolly world of no bugs.

Any views?

11 July 2008 at 09:03


Post a Comment

Subscribe to Post Comments [Atom]

<< Home