Melissa & Joanna FarMarRails submission

[jm-rives]

@PilgrimMemoirs @CheezItMan
https://joanna-melissa-app.herokuapp.com/

[jm-rives]

@CheezItMan

What I worked on in the FarMarRails Project:
Melissa and I paired throughout the project. My individual contribution was styling of the tables and form pages.

What worked well with my pair:
Working with Melissa was the smoothest and easiest pair programming experience up to this point. We established our goal as relationship above product. We were on task, kept ahead of our schedule, discussed the code, the division of labor, and planned our project thoroughly before touching the keyboard. We sought out each other's opinion and worked side-by-side throughout the week. We committed regularly, and had fun. Our work flowed and I was in flow state most of the project. I hope we work in the same shop in the future.

What did not work well with my pair:
There was not an incident that did not go well from my perspective.

Technical parts that went well:
The project went smoothly. We ran into one issue that took 20 minutes to debug, but our user stories fell into like dominos.

Technical parts that did not go well:
We had wanted our splash page to feature a large jack-o-lantern with one eye serving as a link for vendors and another for markets, and planned to add a mouth for guest user on wave 32. We could not get it to style correctly so we settled on using two pumpkins instead. Which we were ultimately as pleased with as if the jack-o-latern had worked out.

Summary: I was extremely pleased with the outcome of this project and had an outstanding experience with pair programming with Melissa.

[olenellina]

@PilgrimMemoirs - FarMar Coding Post

1. What I worked on in the FarMarRails Project:
   My goals with this project included getting really comfortable with navigating a Rails project and understanding the workflow (generating models, controllers, views, etc.). I really appreciated the guidance we were given to take our time and treat this as exploratory, as I didn't feel the pressure to rush through and get something working without really understanding what it was that we did.
2. What worked well in terms of teamwork:
   I loved this pair programming experience and credit that to three things: the discussion we had with Crystal that helped us understand how to navigate the experience; my partner, her support and our communication at the start/during our project; and the guidance given (which I mention above) about focusing on supporting each other and exploring the code. I think we could all use even more guidance on this, so we remember to focus more on our relationship with our pair than the product. We choose to do all of the work jointly, which differed a bit from the instructions, but it was both of our preferences. This helped me as my 2nd pair programming experience was not positive (I felt like I wasn't able to have my ideas heard or explored during Scrabble, and as a consequence, didn't learn or push as much as I could have), so I really appreciated having a second experience to compare this with.
3. What didn't go as well in terms of teamwork:
   Again, the teamwork was my favorite part of the exercise, along with having the time to really explore rails. If we had another week, we probably could have chosen to branch out and do some work on our own, so we could get practice with branching/pull requests.
4. Technical parts that went well and parts that didn't:
   Didn't go well: I suggested that we generate an Index controller for the static landing page, as I thought "well, we might want to add more functionality to it later." I think that was the wrong call, as it didn't have any other functionality and could have been handled by a static page. We also implemented our relationships for the database before Jamie's lecture and I can see that there was a better way to do this, and I'm not even sure that ours works as intended (although, the website does what we wanted it to) :) I'm really thankful for that lecture, as it makes a lot more sense to me now and I'll find time to go back and try this on my own.

Went well: Due to our planning and discussion, very rarely did we try to implement something and it didn't work - I was really surprised by this, as I expected us to have to troubleshoot some things and they just worked!