Merge pull request #5 from INTERSECT-training/lm/update_episodes

Adding material from slides to episodes

Author: lmilechin

episodes/benefits.md

@@ -16,16 +16,16 @@ exercises: 0
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
+Take a few minutes to think about what the benefits of working collaboratively might be.
 
-### Most real\-world projects involve teams
-- Too big to do alone
+Some benefits we have come up with are:
 
-### Produce working code more quickly
+- Most real-world projects too big to do alone
+- Produce working code more quickly
+- Better designs by considering more options
+- Can be more enjoyable
 
-### Better designs
-- Consider more options
-
-### Can be more enjoyable
+The slides for this introduction can be found [here](https://github.com/INTERSECT-training/Building-A-Community/blob/main/presentations/WorkingCollaborativelyIntro.pdf).
 
 ::::::::::::::::::::::::::::::::::::: keypoints
 

episodes/challenges.md

@@ -16,27 +16,32 @@ exercises: 0
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
+Take a few minutes and think about what challenges you have come across when working collaboratively.
 
-### Logistics
-- Location
-- Time zone
 
-### Decision-making
-- Standard practices
-- Designs
 
-### Communication and coordination
-- Who works on what
-- Status
+- Logistics
+    - Location
+    - Time zone
+
+-  Decision-making
+    - Standard practices
+    - Designs
+
+- Communication and coordination
+    - Who works on what
+    - Status
+
+-  Egos (personal factors)
+    - The benefits of collaborative construction are greatly affected by the egos, or humility, of the participants
+    - The Egoless Programmer
 
-### Egos (personal factors)
-- The benefits of collaborative construction are greatly affected by the egos, or humility, of the participants
-- The Egoless Programmer
 > “…most of programming is an attempt to compensate for the strictly limited size of our skulls.  The people who are best at programming are the people who realize how small their brains are.  They are humble.  The people who are worst at programming are the people who refuse to accept the fact that their brains aren’t equal to the task.  Their egos keep them from being great programmers.  The more you learn to compensate for your small brain\, the better a programmer you’ll be.  The more humble you are, the faster you’ll improve.”
 (*Code Complete 2ed.* pg. 821, summarizing a 1972 Turing Award lecture by Edsger Dijkstra)
 
 ### Strive to become an [egoless programmer](https://blog.codinghorror.com/the-ten-commandments-of-egoless-programming/)
 
+The slides for this introduction can be found [here](https://github.com/INTERSECT-training/Building-A-Community/blob/main/presentations/WorkingCollaborativelyIntro.pdf).
 
 ::::::::::::::::::::::::::::::::::::: keypoints
 

episodes/introduction.md

@@ -16,11 +16,17 @@ exercises: 0
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
+This lesson serves as an introduction the the other lessons on Working Collaboratively:
 
-### Some points here about the other modules
-Blah blah blah
-
+- Tools for Working Collaboratively
+  - Collaborative Git
+  - Issues and Pull Requests
+  - Documentation
+- Licensing
+- Project Management
+- Code Reviews and Pair Programming
 
+The slides for this introduction can be found [here](https://github.com/INTERSECT-training/Building-A-Community/blob/main/presentations/WorkingCollaborativelyIntro.pdf).
 
 ::::::::::::::::::::::::::::::::::::: keypoints
 

episodes/social_aspects.md

@@ -17,19 +17,20 @@ exercises: 0
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
-
-
-### Inclusivity
-### Codes of conduct and their enforcement
-### Attitude: “Our” vs. “My” software
-### Engaging with new contributors
-### Group practices
-- Leadership
-- Decision-making style
-  - Egalitarian vs. acknowledged leader
-  - How much autonomy does an individual developer have?
-- Time commitments to the project
-
+The following are some social aspects to consider when working collaboratively:
+
+- Inclusivity
+- Codes of conduct and their enforcement
+- Attitude: “Our” vs. “My” software
+- Engaging with new contributors
+- Group practices
+  - Leadership
+  - Decision-making style
+    - Egalitarian vs. acknowledged leader
+    - How much autonomy does an individual developer have?
+  - Time commitments to the project
+
+The slides for this introduction can be found [here](https://github.com/INTERSECT-training/Building-A-Community/blob/main/presentations/WorkingCollaborativelyIntro.pdf).
 
 ::::::::::::::::::::::::::::::::::::: keypoints
 

episodes/socio_technical_aspects.md

@@ -17,29 +17,27 @@ exercises: 0
 
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
-
-### Remote Collaborations
-
-- Meeting scheduling
-- Need for more explicit communication
-- Feeling “part of the team”
-    - Getting to know each other
-
-### Modes of communication
-
-- Common terminology
-- Helping people at remote sites
-
-### Understanding team expertise
-
-- Science
-- Data
-- Visualization
-- Computer system and language
-
+The following are technical considerations when working collaboratively:
+
+- Remote Collaborations
+    - Meeting scheduling
+    - Need for more explicit communication
+    - Feeling “part of the team”
+        - Getting to know each other
+- Modes of communication
+    - Common terminology
+    - Helping people at remote sites
+-  Understanding team expertise
+    - Science
+    - Data
+    - Visualization
+    - Computer system and language
+
+The slides for this introduction can be found [here](https://github.com/INTERSECT-training/Building-A-Community/blob/main/presentations/WorkingCollaborativelyIntro.pdf).
 
 ::::::::::::::::::::::::::::::::::::: keypoints
 
-- None
+- Technology can augment collaboration, but it is not a replacement for clear communication.
+- Make use of the diverse experience on your team. Different technical skills make a well-rounded team and is a great opportunity for collaboration.
 
 ::::::::::::::::::::::::::::::::::::::::::::::::