Reflections

[MNieginski]

What went well? What lessons will you take away from the experience?

• When it finally came down to it, I managed to get a lot of coding taken care of very quickly, base of the project was done faster than I usually am able to code. I became hyper focused on the project, which is usually something I struggle with.

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

• Once i finally started with an API i understood how to use, that had plenty of documentation to support it, I was able to really get a very good amount of work done very quickly, which helped a lot given my circumstance.

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

• I had to restart my project, my original plan, and API were out of my scope, and the documentation was not as user friendly as I would have hoped.

What will you do to prevent the above issue from occurring in a future project/collaboration.

• To prevent this from happening again, I need to be more aware of my skills, and scope of my thoughts and ideas. As well as being more on top of the project and better prioritization, and be better at reaching out for help when I need it, instead of sitting alone, banging my head against the desk trying to troubleshoot myself.

[krabecb]

Excellent reflection points! Glad you found an API that was easy to understand! And I agree, definitely reach out for assistance, especially if the blocker takes more than 30-60 min + research! ☺️

Here are some things I observed while reviewing the app:

• [x] Styling - a good design foundation to build on
• [x] README
• [x] MVP
• [ ] Replace Welcome to my Giphy API app! with app title
• [ ] Perhaps make search field same height with search button
• [ ] Remove console logs! They are visible in dev tools!
• [ ] Submitting an empty search returns a blank app
• [ ] 🧊 Icebox: user authentication + user can favorite GIFs