Session at DrupalDevDays in Barcelona Spain on June 16th 2012.
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.
At NodeOne we've devised 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.