Phlip
7/4/2008 6:46:00 PM
S2 wrote:
> Yes. I asked to get some devs and PMs together and get an analysis done on
> the migration, what we lose and what we would gain by dropping RoR for
> Java, but "for now we don't have the time. New development should be done
> in Java".
At my day job we use pure XP with RoR. We use promiscuous pair programming,
meaning we switch pairs every 2 hours. We use pure Test Driven Development, with
refactoring & continuous integration. We have a very high velocity and a
vanishing bug rate.
Since I got there, our team has increased to 6, and we will get 2 more as soon
as we remodel. I really doubt we could talk our executives into switching back
to Java, or switching from XP to something else... like "Agile".
Your worksite has issues that prevent your executives from seeing which systems
are working better than others. There's an old adage, "If I had 6 hours to cut
down a tree, I would spend the first 3 hours sharpening my ax".
Your bosses think the more strokes required to cut down a tree, the more
"progress" you made. That's what a 600 line configuration file is - 600 more
strokes with a dull ax.
>> So, no pair programming, and they want to make knowledge transfer easier
>> by reducing the amount of knowledge required. Gotcha!
>
> Exactly. I'm not sure I understand your point?
Exactly... you are not sure? (-;
If you are not pair programming, then knowledge is indeed hard to transfer at
team swap time. So your execs think they can reduce the total amount of
knowledge required. Yet more strokes to cut down that tree!
--
Phlip