3 ms·
This article reads a bit (if only a little bit) like an attempt to rephrase ancient XP advice (which is itself a selection of truly ancient pre-1997 wisdom) in
by twic 11y ago
This article reads a bit (if only a little bit) like an attempt to rephrase ancient XP advice (which is itself a selection of truly ancient pre-1997 wisdom) in a refined but folksy way which won't raise hackles.
Mix in master carpenters = Coaching (kind of - this is an interesting blind spot in the classical XP literature)
Measure twice, cut once = Simple Design and Pair Programming
Collect and codify your standards = Coding Standards
Scrap the shortcuts that don’t save time = no specific practice, but a foundational idea of XP is that we go faster by maintaining high quality
Build modularly = (one of the goals of) Refactoring
I think it's quite a good attempt! Metaphors can be very powerful when they fit. Or should i say, when you're able to work with their grain, rather than against it.
I'm reminded of an older such effort, ARM/CL, which (jokily) rephrased it in military terms, to make it more palatable to serious grown-up companies who would never contemplate the zany Mountain-Dew-flavoured antics of those 'extreme' weirdos:
http://c2.com/xp/ArmCl.html http://c2.com/xp/ArmCl.html