- To learn more than we did at the beginning. Learn how to handle CSV files, and to become better at paired projects.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Pair programming is the way to go, at least to start off.
- Driver/navigator until/if we feel comfortable enough to break off into a divide/conquer approach.
- Talking one-on-one, slack is good to communicate outside of that. Be frank and direct with each other, treat each other with respect.
- "Get it done", better working with others, but can work by yourself if needed. Getting to vocalize thoughts can be a big help. Try to stick to a schedule.
- Spending the time together to get the work done. Bringing different strenghts to the project and being open to the other person's ideas.
- Being at Turing or just meeting up somewhere that isn't home to get away from distractions. Reaching out to Mod 3 students if we feel we've hit a wall.
- Maitaining good communication is crucial.
- Randy: Sometimes 6pm, Randy will check today (Tues 5/30) and get back to JF about a schedule. JF: Timebox to 9pm at the latest on weekdays.
- Working on weekends: we could both come in around 9am and leave around 6pm, but we're both flexible. JF's house is open if we want to let the dogs play while we work.
- Being direct without coming off as confrontational. Just being honest with each other and listening without hangups.
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?
- Randy: Testing is a weakness. Strength -- try to rely on what we know and build from it. Classes and methods, and instance variables.
- JF: Testing is a weakness too, hard to do TDD. Whiteboarding is a strenght, planning before coding.
- We both want to place a strong effort on implementing TDD.
- Program like god. Try to adopt a top-down methodology.
How do you want the group to solve problems when members run into issues with features of the project?
- Present the problem as soon as it occurs. Talk through ideas for solutions to each other, then classmates, then mentors.
- If we both walk away with a sense of accomplishment. Focus on learning rather than just getting it completed.
- Feel like we asked for help when we needed it.