Rethinking Coders - Revision history

Rfs: /* Comparison with the Build Program */

2005-06-08T01:54:47Z

Comparison with the Build Program

2005-06-03T20:10:14Z

2005-01-26T00:45:01Z

Some (preliminary) conclusions

2005-01-26T00:42:51Z

Some conclusions

2005-01-26T00:42:33Z

Some conclusions

2005-01-26T00:33:38Z

Some conclusions

2005-01-26T00:31:36Z

Some problems

2005-01-25T23:03:51Z

Some conclusions

2005-01-25T23:03:26Z

Some conclusions

2005-01-25T23:03:02Z

Some conclusions

@@ Line 35: / Line 35: @@
 * once you teach someone how to write a program, they cannot repeat that task several times in any kind of a useful way
-The build program is quite successful at involving a lot of volunteers at Free Geek, while the coders successer are much more modest (and that may be putting it charitably).
+The build program is quite successful at involving a lot of volunteers at Free Geek, while the coders successes are much more modest (and that may be putting it charitably).
 =Some (preliminary) conclusions=

← Older revision		Revision as of 20:10, 3 June 2005
Line 80:		Line 80:

	Clearly we're not achieving a sustainable pace, and several other points could use some work. But this model fits Free Geek closer than most. We need to adapt it to our needs and prepare an infrastructure to make it work. Specifically, we need to have small enough tasks that are clear enough for us to hand them out to coders such that they can complete them and see that as an accomplishment.		Clearly we're not achieving a sustainable pace, and several other points could use some work. But this model fits Free Geek closer than most. We need to adapt it to our needs and prepare an infrastructure to make it work. Specifically, we need to have small enough tasks that are clear enough for us to hand them out to coders such that they can complete them and see that as an accomplishment.
		+
		+	[[Category: Coders]]

@@ Line 38: / Line 38: @@
 =Some (preliminary) conclusions=
+==Get more organized==
 A common root of several of the problems is that work moves so slowly that coders drop out and work doesn't get done. We can approach this group of problems in two ways
 # speeding up the pace of development and/or
@@ Line 46: / Line 46: @@
 #* better tracking of the status of tasks
-An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[#Extreme Programming at a Glacial Pace]] )
+An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[#Extreme Programming at a Glacial Pace]].)
 ==Repeatable pre-coders program workshops==

@@ Line 37: / Line 37: @@
 The build program is quite successful at involving a lot of volunteers at Free Geek, while the coders successer are much more modest (and that may be putting it charitably).
-=Some conclusions=
+=Some (preliminary) conclusions=
 A common root of several of the problems is that work moves so slowly that coders drop out and work doesn't get done. We can approach this group of problems in two ways

@@ Line 39: / Line 39: @@
 =Some conclusions=
-The biggest overarching problem is that projects move so slowly that coders drop out and work doesn't get done.
+A common root of several of the problems is that work moves so slowly that coders drop out and work doesn't get done. We can approach this group of problems in two ways
 An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[#Extreme Programming at a Glacial Pace]] )
@@ Line 59: / Line 64: @@
 ==Extreme Programming at a Glacial Pace==
-From [http://en.wikipedia.org/wiki/Extreme_programming Wikipedia] comes this list of characteristics for ''extreme programming'':
+Applying the concepts of extreme programming in a more conscious way might also help, but we might find obstacles to this when trying to maintain a sustainable pace. From [http://en.wikipedia.org/wiki/Extreme_programming Wikipedia] comes this list of characteristics for ''extreme programming'':
 * Incremental and iterative developments - small improvements after small ones

← Older revision		Revision as of 00:33, 26 January 2005
Line 43:		Line 43:
	An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[#Extreme Programming at a Glacial Pace]] )		An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[#Extreme Programming at a Glacial Pace]] )

		+	==Repeatable pre-coders program workshops==
	A series of repeatable workshops in basics could happen, comparable to the command line for builders class, for new coders. These could cover:		A series of repeatable workshops in basics could happen, comparable to the command line for builders class, for new coders. These could cover:

@@ Line 1: / Line 1: @@
-=Some problems=
+=The main problems=
 * Projects move very slowly -- way more slowly than expected.
 * People who are the impetus for starting a project often move on before it's completed.

@@ Line 41: / Line 41: @@
 The biggest overarching problem is that projects move so slowly that coders drop out and work doesn't get done.
-An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[Extreme Programming at a Glacial Pace]] )
+An advanced coders group that plans out projects, and identifies the specific tasks to be done would give us a foundation for identifying the next task appropriate to a given volunteer that should be done. This would make us more organized to the incoming coders. (See [[#Extreme Programming at a Glacial Pace]] )
 A series of repeatable workshops in basics could happen, comparable to the command line for builders class, for new coders. These could cover: