Главная
Study mode:
on
1
Introduction
2
Why does it matter
3
Steps
4
Save conversations
5
Adam
6
Why use Codestream
7
Larrys example
8
Using Code Stream
9
Routing Questions
10
Live Share
11
IntelliJ
12
Vendor Locking
13
Refactoring
14
Onprem
15
Search
16
JIRA
17
JavaScript
Description:
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.

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

GOTO Conferences
Add to list
0:00 / 0:00