Re: Quora (group bonding)

[ Follow Ups ] [ Post Followup ] [ Discussions at the Paneris philosophy node ]

Re: Quora (group bonding)

Posted by TimP on Tue Sep 15 18:08:20 1998 In Reply to: Quora (group bonding) posted by

Distribution:

>As Paneris expands its membership we need to formalise the
>the tacic understandings that have been assumed todate.
>1. Paneris is a cooperative, be cooperative.
Except, I suppose for point 5.
>2. Working as a group is difficult, so think of it as a game.
> the particular game to think of depends on the
> type of the group.
> The types I have encountered todate are:
>
>
>
>
>
>
>
Group Members Game Example
One person, no impact on others Tetris DOS.html
Two people, no customer Network Doom PMS
One or more people, plus customer I went to the shops and I bought a Curly Wurly... Gemnet
Paneris Pass the ball New Box
I can't see much different between 2 & 3 except you have less control in 3.
Note that games 1 & 3 end when you fail and 2 & 4 when you get bored :-)
>3. To be a coding member, (and I expect to be a graphic contributor )
> you should aim to contribute some of your code to the paneris corpus.
> Ideally this should happen before working for a customer.
> Even better than contributing some code is modifyig existing code and promulgating the modifications.
> See guidelines.
So we're also committing to reviewing potential member's code?
We might have to put a limit on the length of submission allowed.
>4. Paneris the organisation is about gaining the synergy
> of a group whilst maintaining the freedom of the individual.
> A term I would like to introduce is egoless programming,
> a term that was used in the only successful coding team I have been a member of.
> The essense of it is that 'owned code' is bad code.
> Just as the compiler is your friend so is the reviewer.
Indeed.
>5. Each activity has an implicit quorum, which should be made
> explicit ASAP.
> Every member of the quorum has a veto.
> To ignore someones veto is to expel them from the quorum.
OK. Let's try that. Who is the quorum for the New Box, for instance?
>6. When you have finished something give it to someone else to have a go.
>
>Love
>Tim
Myles

Group Members	Game	Example
One person, no impact on others	Tetris	DOS.html
Two people, no customer	Network Doom	PMS
One or more people, plus customer	I went to the shops and I bought a Curly Wurly...	Gemnet
Paneris	Pass the ball	New Box

Post a Followup

Name:

E-Mail:

Subject:

Circulation:

AlexH	ColinR	JackM	JennyP
KeithH	KrugerD	MikeC	MylesC
NicR	PatickG	TimJ	TimP
WilliamC	WilliamS	paneris

Message:

>>As Paneris expands its membership we need to formalise the 
>>the tacic understandings that have been assumed todate.

>>1. Paneris is a cooperative, be cooperative.

>Except, I suppose for point 5.

>>2. Working as a group is difficult, so think of it as a game.
>>   the particular game to think of depends on the 
>>   type of the group.
>>   The types I have encountered todate are:

>>   <table>
>>     <tr><th>Group Members</th><th>Game</th><th>Example</th></tr>
>>     <tr><td>One person, no impact on others</td><td>Tetris</td><td>DOS.html</td></tr>
>>     <tr><td>Two people, no customer</td><td>Network Doom</td><td>PMS</td></tr>
>>     <tr><td>One or more people, plus customer</td><td>I went to the shops and I bought a Curly Wurly...</td><td><a href='/partners/airflow/gemnet/'>Gemnet</a></td></tr>
>>     <tr><td>Paneris</td><td>Pass the ball</td><td>New Box</td></tr>
>>   </table>

>I can't see much different between 2 & 3 except you have less control in 3.
>Note that games 1 & 3 end when you fail and 2 & 4 when you get bored :-)

>>3. To be a coding member, (and I expect to be a <a href='/paneris/cgi-bin/create_page.pl?graphic_contributors'>graphic contributor</a> )
>>   you should aim to contribute some of your code to the paneris corpus. 
>>   Ideally this should happen before working for a customer. 
>>   Even better than contributing some code is modifyig existing code and promulgating the modifications. 
>>   See <a href='/rules.shtml#Guidelines'>guidelines</a>.

>So we're also committing to reviewing potential member's code?
>We might have to put a limit on the length of submission allowed.

>>4. Paneris the organisation is about gaining the synergy
>>   of a group whilst maintaining the freedom of the individual. 
>>   A term I would like to introduce is <a href='/paneris/cgi-bin/create_page.pl?egoless_programming'>egoless programming</a>, 
>>   a term that was used in the only successful coding team I have been a member of.
>>   The essense of it is that 'owned code' is bad code. 
>>   Just as the compiler is your friend so is the reviewer.

>Indeed.

>>5. Each activity has an implicit quorum, which should be made 
>>   explicit ASAP. 
>>   Every member of the quorum has a veto. 
>>   To ignore someones veto is to expel them from the quorum.

>OK. Let's try that. Who is the quorum for the New Box, for instance?

>>6. When you have finished something give it to someone else to have a go.

>>
>>Love
>>Tim

>Myles

[ Follow Ups ] [ Post a Followup ] [ Discussions at the Paneris philosophy node ]

Re: Quora (group bonding)

Follow Ups:

Post a Followup