Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Importance of Collaborative Development

Posted by Hemos on from the working-together-for-bettering-us-all dept.

Eugene Eric Kim writes: "A few months ago, I wrote an essay entitled, "A Manifesto for Collaborative Tools," outlining a vision for how we can and should be making collaborative tools more interoperable. The article was published in the May issue of Dr. Dobb's Journal and is now available on the web." This manifesto is a good one, particularly if you aren't as a familiar with Doug Engelbart as you should be. There's also some interesting links to learn more about the Semantic Web, and social networks, well worth checking out as well.

2 of 61 comments (clear)

  1. Am I the only one... by Face+the+Facts · · Score: 2, Offtopic

    ...who absolutely positively -HATES- the idea of 'paired programming'? While I wholeheartedly agree with having lots of meetings and discussions during the design phase (requirements, functional spec, detailed design) and during the review phase (post mortem, code reviews) I feel that having two coders on one computer is extremely wasteful and unbelievably stressful.

    When I'm in the 'zone' I can't talk with somebody else, I can't verbalize why I'm writing a code fragment the way I am writing it without getting yanked out of it. If the design is done well, and programmers are fairly equally competent, pairing two of them is going to probably be LESS productive than having only ONE, let alone two.

    The only time I can see paired programming being useful would be in a tutoring way, where coder A that has lots of experience with the codebase is paired with coder B that has never seen it, but this is more for getting coder B up to speed rather than to improve productivity and code quality

    --
    -- BSD or Bust
  2. A good one? by Call+Me+Black+Cloud · · Score: 0, Offtopic

    This manifesto is a good one, particularly if you aren't as a familiar with Doug Engelbart as you should be.

    So...if you're familiar with Doug Engelbart, the manifesto is not good?

    Is that right? I have to dig deep for my 9th grade geometry skills.

    If not familiar, then good. So it follows that if not good, then familiar. Hmmm, I guess I didn't get it right. Still, the sentence is an odd one.