-
What are your learning goals for this project?
- L: Solidify Rails knowledge, specifically understand what is happening in the background, understanding the magic that is Rails
- T: Understanding multi-tenancy and what authorization for that looks like. What the user experience would be like for a project like this. Better understanding the database structure and querying the database.
- C: Getting better at rails migrations and getting better at rollbacks and changing things that were previously implemented in the database. Also jQuery.
- A: Undestanding multi-tenancy functionality and implementing Javascript in a rails project.
-
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- L: Prefer divide and conquer, I'm able to focus better when I can work by myself sometimes.
- T: Prefer pairing, gives me the best confidence. I feel like I can get stuck when I work by myself.
- C: Really like grouping and pairing to discuss, but when working on a specific issue I prefer to work by myself and dive into it.
- A: Pretty comfortable with whatever everyone else wants to do but due to past experiences I feel I have a good idea of how to successfully divide and conquer.
-
How do you communicate best? How do you appreciate receiving communication from others?
- L: Face to face. I don't really check Slack.
- T: Face to face but Screenhero or Slack is fine.
- C: I prefer face to face but I'm a slack junkie.
- A: Face to face is fine but I prefer Slack because it helps keep me organized and not forgetting things.
-
How would you describe your work style?
- L: Similar to my collaboration style - I work well in a group but need that alone time as well
- T: prefer to work at Turing and having resources around me, and having goals helps me be successful
- C: I like working at Turing. I'm pretty intense about my projects and get consumed in it so I sometimes need people to tell me when it's time to quit.
- A: I have a pretty adaptable work style, and efficient.
-
What’s gone well or poorly in your previous projects?
- L: Things start getting tense when I feel tired at the end of the day because I'm a morning person. I have the time to stay late but when I'm tired and hungry things start not being as productive.
- T: Well - when we all had a clear expectation of what we're going to get done that day and how long we should stay. It really helps me to have an idea of how the day is going to go. Not well - I'm an empath so if people are distant or something is going wrong I need to know or I can't stop thinking about it. Also, I feel like sometimes my suggestions are not taken seriously.
- C: Not well - I sometimes have blinders on when I get on a track and need to be told firmly a different suggestion. Also the relationship of the group hasn't been that great and everyone was stressed the whole time and didn't discuss it until the project was over. Well - been grouped with technically strong people.
- A: Well - pretty much everything has gone well and people have been very understanding about my schedule and that I can't be here all the time.
-
What do you need (resources, environment, communication) to do your best work?
- L: I get distracted and I need to be able to focus by myself. When I drive I feel like I'm not understanding the concepts as well.
- T: I like switching drivers and want us to be mindful of switching it up. I feel like 2 hours is a good time limit on that. And I need to be able to take naps.
- C: I like to be here and work well here. If everyone is not focused and wants to take a break and go home that's fine, but while we're all together I need everyone to be focused.
- A: I mostly just need understanding of my schedule and that I can contribute to stuff later in the evenings when you all are ready to go home.
-
What scheduling restraints do you have? What are your scheduling preferences?
- L: I'm here at 8:30am. I can stay late but would prefer to leave by 7:45pm.
- T: Yoga class Saturday morning that I don't miss. Otherwise totalling open. Not very good at working from home so if I'm home I probably am done for the day except for answering questions if needed. SAB 4:15-5:30
- C: I'm here to 8:15 to 8 every day. I prefer to not come in on the weekends. I can come in on Saturday if needed. but really not on Sunday.
- A: I'm here at 8:00am. Scheduling is not super consistent. Can usually stay til 6 and then work remotely around 9pm. Can stay til 8 with some notice. SAB 4:15 - 5:30. Saturday can maybe do 1 to 4ish but Sunday is all remote.
-
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- L: Just say it. If I have an issue I will just pull them aside and talk about it.
- T: I usually start with a question because I want to hear about what's going on with them before jumping to conclusions. My fear of hurting someone's feelings does hold me back from giving feedback sometimes.
- C: During a project, I will just ask, are you sure this is going to work? This is why I don't think this will work but tell me why you think it will. Mid project DTR.
- A: Really like feedback in the form of retros.
-
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?
- L: My strengths are finding holes in projects that need to be patched. Finding edgecases. But I need to learn how to prioritize those, too. I also get distracted so working under pressue is difficult for me. Maybe test out putting me under pressure and then check in with me and see how that felt.
- T: When other people are driving I'm able to stay on top of what's happening. I'd like to get better at writing tests and feeling more confident when I'm driving and I might be a bit slower at coming up with the logic than others. Give me the space to come up with the next step and providing me with leading questions so I can make the connection to myself.
- C: I'm good with ActiveRecord querying. I feel strong with Ruby logic. I could use improvement on timeboxing. If you see me working on the same thing for multiple hours.
- A: I feel technically strong generally but am intimidated by the creativity required when the goals are more open ended. So you all could help me with just brainstorming ideas and writing user stories together, collaborate on what they mean.
-
What tools do you want to use to manage the project?
- L: Waffle
- T: Waffle
- C: Waffle
- A: Waffle
-
How do you want the group to solve problems when members run into issues with features of the project?
- : Timebox to 20 minutes, can extend to 30 minutes if you're really close. At the cutoff point, inform the group of what you've tried, where you're at, and ask for suggestions on what to do next.
-
How do you know if a project is successful? How can we achieve that as a group?
- L: When you're feeling good about it and proud about it. Feeling okay even with the loose ends that might not have been tied up. User stories have been fulfilled. We can get all the base functionality achieved and then work on the extras.
- T: I feel like intimacy with the code base is something that is important to me so that we can feel a sense of ownership over it. Trading off drivers and making sure we're all contributing equally.
- C: When you're proud of the project and it's done and what you've learned. We should be invested with it and listening to all ideas.
- A: For me I don't need to be intimate with the code, but I want it to be understandable to all people. Success to me is everyone learning, everyone contributing, everyone having their ideas heard.
Any additional questions that you would like to add:
-
Git workflow:
-
Angela - team leader
-
Development branch is checked out from master
-
Don't merge your own pull request
-
Add comments if working with a pair and submitting a pull request indicating who is with with you reviewing the code
-
2nd person to review the code can merge the pull request
-
for a WIP PR, add good comments to indicate the problem
-
Rebasing - remember to rebase from Github when merging a PR if needed! and let people know to rebase as they do the merge if you're unable to do it from the command line.
-
Group retro:
-
First one Friday at 10
-
Tuesday final push retro
-
Post eval on Thursday