/* TALKING ABOUT CODE */

When you're just one person, or three, knowing how something is done or why is not that hard. You can rely on comments in code, and when necessary ask the person. But as your organization grows it gets harder. Your group, team or company becomes a repository of knowledge, of how a certain website works, of why a module was written a certain way, or how something should be done. But this repository is increasingly hard to search and access. This session focuses on tools and processes to handle this in order to help you manage and applying your company's shared knowledge.
In this session I will share several ways to keep knowledge flowing between developers, even as teams grow.
IN THIS SESSION ON KNOWLEDGE MANAGEMENT FOR DEVELOPERS AND TEAMS I WILL TALK ABOUT
The problem of obstacles to sharing knowledge of solutions, implementations or projects.
How you can organize your projects and schedule to make exchange of knowledge easier.
Ways to work that helps share knowledge and information between developers.
Tools you can build in Drupal that will help you store and share, and turn that "tacit" knowledge Joe has, into something searchable and available to Karl who was just hired.
Previously presented at the Drupal Dev Days in Barcelona, Spain in June of 2012.
ABOUT THE SPEAKER
Jakob is a Drupal expert and works as a business and web consultant. Jakob co-founded NodeOne/Wunderkraut and has worked with customers devising web strategy as well as with intellectual capital and knowledge management. He's been working with Drupal since 2005 and has a background in cognitive science and computer science.
Jakob has previously been speaking at DrupalCons and DrupalCamps on estimating techniques and on NodeOne's platform distribution NodeStream.