Yes, I think all of these are great. I believe the XP method of team
programming will work with fine. one person sends their code to the head of
the team for him to review it and then once they are done they send it back.
This way the coder can see if any changes have been made and they can learn
from mistakes amd also new coding tips and hints or maybe nothing at all and
they move on to the next step.
-Shawn Regan
-----Original Message-----
From: Steven Brownlee [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 07, 2001 5:41 AM
To: CF_OpenSource
Subject: RE: Code Police what do you think
Not just one person. We could use a modified XP (extreme programming)
approach where each developer is always responsible for examining
another developer's code. In fact, I think there are a few concepts of
XP that we can use.
* Simple design - This means that complexity in the system is eliminated
as soon as it is discovered.
* Testing - Each developer is responsible for authoring test units which
must run without errors. Extensions to the code, or allowing other
developers to modify the code should not be allowed until these tests
are passed.
* Collective ownership - Any developer can change any code at any time.
* Metaphor - This term is used to describe the shared vision of the
entire project and how it works
* Coding standards - This has already been addressed.
* Pair programming - In XP two programmers are always assigned to one
workstation for development. Obviously that won't work here, but it can
be modified to work for us. Each task will be the responsibility of two
developers. They have to decide how to split/share the work, write the
tests and maintain standards.
I know this is possible, but its getting everyone to agree to it that's
always the problem. Any thoughts on these?
**Steve
-----Original Message-----
From: Robert Everland III [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 8:19 PM
To: CF_OpenSource
Subject: Code Police what do you think
Someone has suggested to me offline that we have someone who
acts as the code police for the project. Thier duty would be to scan
each piece of code to double check to make sure it is optimized as much
as possible and has all things as specified in the futuer coding
standards. What do you think as a group?
Bob
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
