Yael and Leah FARMAR!

[lbueing]

https://yaeleah.herokuapp.com/
@CheezItMan @PilgrimMemoirs

[ghost]

@PilgrimMemoirs

we worked on the 'skeleton' of the project together - meaning all the market admins parts of it.
then I was working on vendors and Leah was working on the visitor. Leah was also in charge of css which we did partially together but leah was leading (which I'm grateful for :))

as a team we worked very well together I think. we have similar preferences on how to structure things in terms of how much work and of what kind should get done together vs separately, as well as similar preferences regarding giving and getting feedback (and similar preferences reg. snacks!)

we both don't really like css... but we managed to live through it well :)
If I absolutely have to find something that wasn't as good about team work - is that I was a tiny bit burned out at the last part of the last day... so that meant Leah had to stay in charge of css and I was just helping... in other words - what didn't go well was me in the last couple of project hours.

we never ran into major bugs.. we managed to solve most things pretty easily and smoothly. we had an issue with having our images shown in the heroku website - I think that was the only thing that took longer to handle... and we got over it too - with some help from Emily and the posts on slack that related to it.

[lbueing]

Yael and I worked on the Markets Admin portion of our site together as pair programming. Once this was completed, I worked on the Visitor portion of the site, and began the initial pieces of the CSS. Once we were both working on CSS we completed the 'look' of our site together.

At the beginning of our project, Yael and I took some time to discuss the particulars of our work habits, strengths, weaknesses, etc. This was incredibly helpful, mainly because I believe it allowed us to have very candid conversations during the project knowing that we both value straight-forward honesty, and both have tendencies to be direct. We were able to work effectively and easily tackle problems as they arose.

We were fortunate to not have any major teamwork difficulties, and the difficulties we did encounter were simple things like how we want the layout and flow of our site to be, given that we had our own visions of what it should be. Each small difficulty was met with a discussion of view points and reasoning, and ultimately ended in a compromise. Perhaps not a partnership difficulty, but one that involves both partners, was simply the timing of completing our project. The pair programming in the beginning helped us both get on the same page, but it did take a long time, and we were working up until the very last minute.

I believe the most challenging part of the project was understanding the larger layout of the site and how each page connected to other pages. To complete our idea of how we wanted the site to function, we had to go back and add extra pages to account or differing functionalities of admins and vendors. The CSS proved tricky as well. Particularly one annoying issue with finding how to change properties of buttons. Otherwise, there were surprisingly few technical difficulties.

@CheezItMan