- What are your learning goals for this project?
Ethan: integrating contracts on the BC Nick: implement simple blockchain (~ CRUD todo app in Rails) David: interested in the planning aspect (linking up different contracts) Mike: simple BC, test-driven React
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Ethan: Divide and conquer, but might need to pair more because of new terrain (hybrid) Nick: DC if it's brand new or super routine, pair for the middle stuff David: Prefer DC, pairing for conceptual stuff, planning/design Mike: nothing new to add.
- How do you communicate best? How do you appreciate receiving communication from others?
Ethan: Clear and responsive (slack, gh) for both. Nick: Echo. Stand-up appraoch (this is what I'm working on...). David: Direct feedback, and rapid. Mike: cascade comm medium based on availability.
- How would you describe your work style?
Ethan: Divide and conquer, but looking forward to the collaboration. Good comm flow. Nick: Echo. Competent solo if direction is known. David: less organized, but has gotten better. Likes learning new things. Mike: Slow to start, but finds ways to optimize
- What’s gone well or poorly in your previous projects?
Ethan: Cloney Island had no project manager. Handle white-water with more intention. Nick: Lack of consistency in the "voice" of the code. Good tracker flow. David: Keep direction and final goal in mind, frequent and snackable PR's. Mike: Lack of communication, distribution of work.
- What do you need (resources, environment, communication) to do your best work?
Ethan: resources TBD! Prefers some solo time. Clear and direct. Nick: Grouped Solidity learning, chat to get consensus, then move to solo work. Direct clear comm. David: configurable dev environments agreed upon, pastries. Mike: Similar to the rest.
- What scheduling restraints do you have? What are your scheduling preferences?
Ethan: Pretty flexible. Nick: Phone calls and cold outreach. 8-9am 5:30-6pm. David: "Pretty much good to go." Mike: Wednesday anniversary, match times.
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Ethan: Fear of hurting someones feelings, but hasn't been a huge problem at Turing. Nick: In person preferred. Holds back if it seems obvious. David: Feedback in small quantities, say it soon. Quick feedback loop. Attitude of impermanence holds back. Mike: Biggest restraint is fear of conflict.
- What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?
Ethan: + in solidity, still working on testing in solidity, unclear about how to connect contracts Nick: + in clean, organized, tested code, - in solidity, looking for help in handling the breadth of resources. David: + in the Truffle environment. - in how the datatypes work, and wants to learn how. Share your tidbits. Mike: + in JS, React. - in solidity and ethereum. Concrete resources.
- What tools do you want to use to manage the project?
Pivotal Tracker, Slack, Github, Screenhero, test RPC and Truffle.
- How do you want the group to solve problems when members run into issues with features of the project?
Timebox 30 - 60 minutes, then seek help. Rubber duck.
- How do you know if a project is successful? How can we achieve that as a group?
Ethan: Agreed upon MVP. Nick: Solid portfolio piece. Half over half assed. David: Be proud of it. Mike: It works and it looks good.
Any additional questions that you would like to add:
Project Ideas:
Stack Overflow type model Financial model
- Branches: PIVOTAL_TRACKER_NUMBER-initials-description-of-card
- Link PRs in PT comments
- [#PIVOTAL_TRACKER_NUMBER] in every commit
- "...so that" or "because" to close stories.
- Talk about how you would use this