I think that a wiki or a internal blog could be excellent to document useful procedures for all team members.
But another interesting point is the communication between programmers when some programmer has a implementation doubt. For example: a programmer doesn't know how to implement some functionality. So, it could post your doubt in a "short messages application", like a twitter (but with more than 140 chars). Then, some developer that knows how to solve her doubt could post the solution. All the messages will be stored until the solution was found. So, all the other members of the team will look to this solution in future.
I think that this schema is nice, because sometimes the developer doesn't like to "waste a lot of time" writing a post on blog or something on wiki.
