Why Development Teams are Throwing Away Institutional Knowledge - and How to Preserve It

Explore strategies for preserving institutional knowledge within development teams in this 44-minute conference talk from GOTO Chicago 2018. Learn why development teams often lose valuable insights and problem-solving approaches, and discover practical methods to capture and retain this critical information. Examine tools and techniques for saving code-related conversations, routing questions effectively, and integrating knowledge preservation into existing workflows. Gain insights on using platforms like CodeStream to enhance collaboration, improve code understanding, and maintain a searchable knowledge base. Understand the importance of avoiding vendor lock-in, leveraging live sharing features, and connecting preserved knowledge to issue tracking systems like JIRA. Apply these concepts to refactoring efforts and various programming languages, including JavaScript, to build a more efficient and knowledgeable development team.

Introduction
Why does it matter
Steps
Save conversations
Adam
Why use Codestream
Larrys example
Using Code Stream
Routing Questions
Live Share
IntelliJ
Vendor Locking
Refactoring
Onprem
Search
JIRA
JavaScript