DTR Project: Night Writer Group Member Names: Timo Mitchel, Iza Jimenez Project Expectations: Open communication, falling through on responsibilities, not procrastinating, good time management. What does each group member hope to get out of this project? Developing better programming skills and understanding - improving enumerables practice . Facilitate good learning practices.
Goals and expectations: Finish strong, finish early. Both persons understand all components of the code, and explain thoroughly. Have time to refactor. Follow rubric and use irb/pry to test implementation. Make good tests. Share good references and resources! (i.e. visual representations). Share tips on using atom/terminal shortcuts. Make each other faster/better developers overall.
Team strengths: Timo: Persistently works through projects and hurdles. Will make Iza take breaks. Iza: Programming aesthetics
How to overcome obstacles: Empathy towards each other’s learning style. Asking for help from upper mods, not waiting too long before asking for help. New set of eyes looking at code to present different ideas - help constantly progress.
Schedule Expectations (When are we available to work together and individually?): Open availability during weekends - otherwise, Slack. Brainstorming ideas on day 1, bringing together findings and ideas. Working through steps.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Be up-front and direct with communication. Touch base when working separately. Primary - Slack (No snooze)
Abilities Expectations (Technical strengths and areas for desired improvement): Build on strengths, if one team member is stronger utilizing certain methods, talk through process - be the navigator. Switch roles for logic and thinking...and typing. Learn file reading.
Workload Expectations (What features do we each want to work on?): Tackle tasks simultaneously, especially parts both individuals are not too strong at.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Practice utilizing terminal with GitHub - push/pull requests, git init/commit, git add, git status, git log, hub create. Ping-pong.
Expectations for giving and receiving feedback: Ask pro-active questions on any discrepancies. Comfortable with accepting constructive criticism - responding with feedback and solutions to problems. Feedback sandwiches : criticism sandwiched between positive stuff...
Agenda to discuss project launch: Individual brainstorming and research. Breaking down project into smaller tasks and how to approach each method and step. Research IO file writing and reading, after organizing what we already know. Start working together tomorrow.
Ideas: Pseudocode first. Don't be afraid to backtrack if progress slows and current problem needs new approach. Code is cheap!
Tools: ScreenHero, Google Hangout
Additional Notes: Celebratory drinks after evals.