- Joel: File reading and writing. Modules. Usage of multiple classes and data strutures. Testing
- Padraic: Moving data around classes in an efficient way. Utilizing modules. Writing more appropriate tests.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Joel: Verbally processing before moving forward on coding decissions. Driver navigator
- Padraic: Divide and conquer. Using more split responsibilities. Having a strong knowledge of the scope of the project so we feel comfortable breaking off and working on portions alone.
- Joel: Slack. Diagraming and markerboarding.
- Padraic: Slack.Talk through verbally to actionable items together.
- Joel: Limited screen time if frustrated, move to paper diagraming and spitballing. Take frequent breaks to refresh your mind.
- Padraic: Diagram/Whiteboard as much as possible. Delve into a class until you can't say anything more about it.
- Joel:
- Good: Logic, Diagraming, Debugging.
- Bad: Still weak on some of the basics.
- Padraic:
- Good: Willingness to work through things. Using enumerables.
- Bad: Haven't been completing on time. Lots of unneccessary instance variables in classes.
- Joel: Change of environment. Patience when I come up short on knowledge. Checking in on others.
- Padraic: Change of venue. Communication. Not staying frustrated too long. Working through issues as soon as possible, so neither of us are wasting time.
- Joel: Has 3 kids and wife. After school for an hour or 2 is good. Sunday morning until Noon is good
- Padraic: Has a dog.
- Joel: Verbally if possible. Slack too.
- Padraic: Slack.
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?
- Joel:
- Strengths: Finding ways to back ourselves out of the corner.
- Need improvement: Writing better methods. Sharing between classes.
- Padraic:
- Strengths: Understands Ruby syntax very well. Can debug very well.
- Need Improvement: Seperating methods. Dividing classes into more diverse functionality.
- Slack Channel
- Git Hub Pull requests.
How do you want the group to solve problems when members run into issues with features of the project?
- Assess where the problem lies.
- Talk out possible ways to solve.
- Diagram (whiteboard) and write out solution until one makes sense.
- Attempt to execute
- Fully functional
- If contributors come away with more knowledge than they started with.
- Use of good coding practices.
- Use enumerables and write readable code.
- Lots of GitHub commits
Not at this time. Thank you for asking!