search

MNieginski / Seaside_Shenanigans_Squad

0 stars 3 forks source link

Issue 3: Reflections #43

Open lauriehimmel opened 1 year ago

lauriehimmel commented 1 year ago

1. What went well in building the project? What lessons will you take away from the experience?

Our team had excellent collaboration. Our communication and support allowed us to work through problems and not get frustrated. We'll definitely take away the benefits of approaching code and collaboration with a positive attitude.

2. Is there anything about your efforts/workflow you want to reproduce in future projects?

Being supportive and open to trying different problem-solve suggestions from peers.

3. What did not go so well? Were there any events/obstacles that blocked you or impeded your team’s progress?

We could have implemented more async time - we all enjoyed the group collaboration, but think that with some additional async time we could have possibly implemented some more features.

4. What will you do to prevent that from occurring in a future project/collaboration.

Delegating after-class tasks/time specifically, to make sure we can work asynchronously and not have merge errors.

krabecb commented 1 year ago

TTT (Laurie, Mikal, Pino) Heroku: https://scenic-shenanigans-edd3a3d09050.herokuapp.com/ PROJECT PASSED Instructional Glow: README, styling is very appealing/minimal, code is organized. Very awesome and well executed concept! Great work on models! Great use of regex, data parsing, AI! Instructional Grow: Include stretch goals! Any APIs that would pair well with this? SASS? A lot of client-side data validation -> refactor to BE controller. Separation of concerns with AI integration. Vacations controller appears blended with upload functionality. Separate controller for uploads and AI.

Grow Snippet

  1. Possible additional controller operation to check / update many across all vacations where companions might relate to the deleted user is a quick refactor.
  2. See earlier point, when model delete an primary resource(vacation) where association occur you will also have to run updates for the related documents (users).
  3. Agree. More modular api routes for common user looks and utility features for client side data validation could be nice - keep the EJS focused just on rendering content, rather than parsing and updating content. Let the database/api do the data lifts!