Reflections

[Echoesong]

What went well? What lessons were taken away?

• Working around our team's strengths and weaknesses to make a good, functional app while also putting ourselves outside our individual comfort zones to grow our skillset.
• Lessons: Git flow, pair-programming flow, teamwork

What do you want to reproduce regarding efforts / workflow?

• Asking for help/pair programming where necessary. Don't just plug away at your own problem for too long, rely on your team.
• Be on the same page for Git flow, it will make things go smoothly. We did a good job with this on this project.

What obstacles / roadbumps were run into? What could be done in the future to prevent a similar obstacle from arising?

• We spent a long time figuring out how to get one piece of functionality working, specifically our delete function for our sub-document. We've mentioned it several times at this point, but it was quite an eye opening experience to have a question we spent 2+ hours researching answered directly on the Notion document.
• To avoid this sort of situation in the future, we should begin by using the resources that are most readily available to us. In this example this would be the Notion document, but in a future development environment this could be something like internal team documents/wikis; after those resources are exhausted, then we can move on to other resources like StackOverflow.

[maker-jws]

Great summary of your teams / strengths and challenges. No major concerns here, you presentation content and overview was professionally delivered and engaging and reflects your teams cohesions / communication. Great work.

Other instructor notes: UI/UX - Looks very professional. Bootstrap! Design - Maybe make use of negative space / container and table row padding for legibility. Code quality - Code is clean and spacing is consistent. Responsive design - Very impressed by the app's mobile responsive design.

Future features - Authorization for U/D is essential for scaling the application. Adding a Favorites and/or following functionality feels like a natural extension of the auth functionality for a post-GA refactor.