Last active
September 8, 2015 17:49
-
-
Save 7hoenix/e9b5ade10d4f8fb60f2c to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1) What habits of your group members are you hoping to adopt? | |
JH => Optimism. | |
JP => Very effective communicator. | |
Bret => Use pry to go through the code a lot. | |
JH => Just start typing. To get going. Instead of waiting | |
JH => Doing one thing from memory and then copying it (instead of just copying old code). | |
Bret => Keeping organized and logical. | |
JP => Wanting to learn why things work they do. | |
2) Give an example of something you think too much time was spent on (bad choices, rabbit holes etc). | |
Bret => Saturday was terrible because both JH and Bret went down huge rabbit holes and wasted several hours. | |
Not running pomodoro clock was a big mistake on Saturday. | |
Yes, decisions absolutely improved as Bret noticed the pattern on Sunday. | |
3) Give examples for each of the following areas. | |
Technical things that pushed the team forward: | |
Finding solutions that already exist (like the URI gem). ActiveRecord methods that already exist (find_or_create_by). | |
Non-technical things that pushed the team forward: | |
Chatting with other groups. | |
Taking breaks. | |
Technical things that hindered the team: | |
Not knowing ActiveRecord. | |
Bad use of git definitely hindered us at first. | |
Non-technical things that hindered the team. | |
Different working styles (especially different ways of tackling problems). | |
4) What steps did you take to manage stress that were effective both individually and as a team? | |
Not enough sleep all the way around. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment