Team PupDates: Andrew Johnson, Matt Malone, Sam Coleman, Sara Karsh
Guiding Questions to Define The Relationship:
- We’re all here to learn new languages and frameworks and we all want to know all the parts of the code base
- Have a polished project to hopefully present at Demo Comp
- Treat it like it’s a job
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Andrew prefers pairing but as the lone back-ender he will be working alone. However, for pairing practice and because we’re all interested in backend, he’ll be walking us through the code as needed
- Sara: I like a mix of pairing and working solo. Generally need to be alone with a problem, then go back to pairing/group work, then back to divide and conquer. Kind of an agile flow
- Sam: prefers pairing for the bigger problems and divide and conquer on the smaller things
- Matt: likes a mix. Big pieces together, small pieces separately.
- Andrew: consistent honest feedback and constant communication. Message anytime
- Sara: consistent honest feedback and constant communication
- Sam: be clear, constant communication
- Matt: provide specific feedback, be open and honest
- Andrew: even-keeled and persistent
- Sara: perpetual motion, but keep perspective. Keep the stress minimized
- Sam: plan ahead, always use a struggle timer
- Matt: great at talking things out and providing support to partners. Also able to really dial in and accomplish a lot.
- Andrew: buffer; mold to the role needs to be meet. Keep things balance
- Sara: frequently mediator; keep things in perspective, don’t let problems get blown out of proportion. I love problem solving
- Sam: effective communication, anticipating potential problems before they arise. Testing, clean code
- Matt: positive attitude, clean coder, problem solver.
- Andrew: poorly - people dropping off the radar and not communicating. Well - taking the time to go through the set up, both personally and technically.
- Sara: poorly - people dropping off the radar and not communicating. Well - communicating consistently, having a clear picture of each of the pieces of the app and overestimating the amount of time things take
- Sam: poorly - people dropping off the radar and not communicating. Well - anticipating time management problems and constant communication
- Matt: poorly - having people not be clear about their work availability. Well - being able to work together and share problems and goals
- Open discussion to present the options but quick decision making so we’re not waffling on one thing for too long
- People: open discussion, provide specific, actionable, and kind feedback and implement said feedback
- Tech: research, ask for help, get an outside set of eyes when needed
- Matt: plan as a group, build out big pieces together, then when the smaller stuff comes up work on it independently with clear expectations
- Andrew: solo spike to figure something out and then pair
- Sam: depends on what the problem is; sometimes working alone, sometimes working around trusted resources for help
- Sara: depends on what I’m working on. Sometimes need to be alone, sometimes need to work around other people for resources
- Christmas and New Years
- Matt is traveling for the holidays
- Matt and Sara are morning people who go to sleep on the early side
- Sam traveling Dec 22 to Jan 3
- Andrew traveling 22 thru 29th
- Sara: very direct, but kind
- Andrew: prefers being direct and honest
- Sam: tell it how it is
- Matt: cognizant of not speaking out of emotion. Provide constructive feedback and if that’s not possible, then sit on the feedback until a time when a solution is present
- As a group, when providing feedback, present a solution. Don’t bring up a problem without having a way to remedy this
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?
- Andrew: likes database stuff a lot; not strongest at testing consuming APIs
- Matt: write solid JS code. Needs improvement in testing
- Sara: write readable code; need to improve React-esque testing; UI/UX stuff is not a big strength. Also good at Redux, if we need to use it
- Sam: good at React which should translate to React Native; good with PRs and workflow
- We’re going to use GitHub projects
How do you want the group to solve problems when members run into issues with features of the project?
- Google it and ask for help
If it’s completed and we pass. If we’re all pleased with the outcome and our experience working together How will we recognize each other's successes and celebrate them? With a smile and a high five. Express appreciation often.