Raising the bar

This is the Software Craftsmanship Wiki which plays the role similar to that of the C2 wiki in the formation of a nexus of practices/techniques/ideas around Extreme Programming.

Note to all: this wiki is really in its infancy. Don't be afraid to add content anywhere, or restructure things to make them more readable writing essay for example.

So you want to contribute?

  1. First things first, create an account!
  2. Learn the wiki syntax by editing away in the playground page
  3. Now you're ready to take a look at the ToDo page
  4. .. and some guidelines

Paths to go from here

Visit Page ideas. It's a place to just jot down those semi-concrete ideas we all have at times. They might then be moved to the appropriate place in the rest of the wiki later, when they grow up.

If you want to participate in active discussions about Software Craftsmanship join the software craftsmanship google group!

Read a book related to SC? We have a bibliography section listing books we consider can help you out in your journey.

Twitter your SC actions! Click #scaction to view live feed from Twitter. (this seem to be not so active these days)

Pair programming has been discussed a lot lately at the mailing list. One suggestion was to add a page listing companies that use pair programming. Here it is: PairProgrammingWorkPlaces.

SCTAGS survey September 2009. 36 mailing list participants expressed their view of the software craftsmanship movement by using three words or phrases only. The result is a word cloud that can be viewed here: SCTAGS2009 Word Cloud.

User Groups. List of software craftsmanship users groups. Please add your groups information.

SEE: research paper help

Back to top
frontpage.txt · Last modified: 2010/07/28 15:58 by Rocky Milby

© 2009 The Software Craftsmanship Community