We would like to finish the project while meeting all expectations and trying extensions. We hope to increase our understanding of encryption through this project. We also look forward practice pairing on a project.
- Proactive
- Willing to learn and work
- Look for feedback
- Experience writing an encryption program
- Project planning experience
When faced with an obstacle, we plan on:
- work harder together on solving the issue
- if that doesn't work, we will step away
- come back to approach from a different angle
- set a time limit for when we get stuck
Mornings 8-9 Lunch Evenings can do 4-7 Weekend: Saturday Flexible and Sunday afternoon (post 2pm)
##Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): We will communicate frequently on the pieces of the project. Our primary method will be face to face. However, we may also lean on Slack and Screenhero for non-in-person communication.
We both felt comfortable that we would be able to write the logic for this program. So we would like to focus on breaking this logic into single purpose methods through encapsulation and keeping the methods short. We want to be better Test Driven Development.
Largely, we plan on working on the features of this project together.
We will work in-person on features using the Driver/Navigator method. If we decide to divide-and-conquer then we will use:
- Branched features
- then review code together
- merge/do pull Requests
We are both OPEN and want all the feedback, don't hold back.
- Review project requirements
- Talk about features/development phases
- Decide on pair styles
- Plan feature/deliverable schedule
- "White Board" pseudo code to break down the logic
- Git
- Rake / Minitest
- Rubocop
- SimpleCov
- Devver's Construct (for Mock file testing)
- Slack
- VS Code / Atom