From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] XP (was: code complexity)
Date: Wed, 6 Feb 2002 11:42:04 +0100 [thread overview]
Message-ID: <3C61087C.6E71A80F@strakt.com> (raw)
In-Reply-To: <20020206001339.2FBC619981@mail.cse.psu.edu>
geoff@collyer.net wrote:
> I haven't read enough about XP to comment on most of it, but I dislike
> the idea of pair programming.
Depends of the circumstances.
> There's nothing wrong with someone else
> reading my code, but I need some quiet and calm to program, so having
> someone nattering in my ear, second-guessing me is going to be a
> disaster. And how is the other member of the pair selected?
Well yeah, that is a problem. At least here we're a small group and
are going in the same direction. Pair programming in a large group
[real world] would be a disaster (unless you like being lectured or
yelled at :).
We don't do it that much, but sometimes we do, when we want to, with
who we want to. Then again, I guess I am pair programming right now
with a guy 30km away [we are discussing protocol implementation issues].
> Go it alone?
I'd go for the 'go it alone' but call in for help when I/you need it.
next prev parent reply other threads:[~2002-02-06 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 0:10 geoff
2002-02-06 0:29 ` [9fans] code complexity George Michaelson
2002-02-06 10:47 ` Boyd Roberts
2002-02-06 20:49 ` Andrew Simmons
2002-02-06 0:47 ` [9fans] OT XP (was: code complexity) Matt H
2002-02-07 10:33 ` [9fans] OT pair programming Boyd Roberts
2002-02-06 10:42 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-05 17:40 [9fans] XP (was: code complexity) iwanek
2002-02-05 17:49 ` Boyd Roberts
2002-02-06 20:15 ` Laura Creighton
2002-02-06 23:04 ` Steve Kilbane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C61087C.6E71A80F@strakt.com \
--to=boyd@strakt.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).