- When I work in a team I like to ensure all group members are on the same page with our goals for that day and the order in which we want to work on them. For this project, we typically used the first 5 minutes of our meeting to discuss the roadmap for the day so everyone was in agreement on that day's workflow. This kept us on task, organized, and allowed us to lay out a timeline that would allow us to finish the MVP before the deadline.
What was a specific technical challenge your group faced? How did you approach this challenge? What went well? What was a struggle?
- We stuggled to have our DOM reflect the changes in the data model. We realized this issue was coming from a lack of understanding in event delegation, so we took a break to review that lesson. We found it really helpful to revisit the CodePens we completed in class to see examples. We also really took advnatage of using console.log statements to help us understand where we were running into the issue.
- This project showed me that I take great pride in my code and attention to detail. There were times we could have moved on without perfecting our layout, but I wanted to match the comp as close as possible. I realized I value writing the best code I can even when it means taking extra time and not getting to the extensions.
- I learned so much about data model / DOM manipulation. I now feel comfortable rendering the DOM to have it display changes in the data model. I also know how to use console.log's throughout the project to ensure both the DOM and data model are being updated. I also learned that bugs can pop up really quickly so it is important to constantly be checking your data model and DOM everytime a new feature is added.
- I would like to finish my next project at least a day before the deadline so if any bugs pop up I have time to address them. We had a bug pop up the day this project was due which was very stressful. We were able to fix our code before the deadline but I do not want to still be resolving issues that close to it again.
- Usually I play the role of the organizer and motivator. For this project, that meant I created a schedule for which iteration we should complete each day to finish all 5 by Sunday. I kept an eye on our progression to make sure we were following our timeline and provided encouragement to help us keep our spirits high.
- I first like to check my notes and the lesson plan. If I am still stuck, then I like to check StackOverflow or the MDN Web Docs. If after 30 minutes of research I find myself still struggling, that is when I like to reach out to my classmates. If people are working in Study Hall, I like to join the zoom and ask my question there first. If people are not in the Study Hall Zoom then I post my question in our Slack channel. If all else fails, I would reach out to my mentor or rock.
- One personal takeaway is that rarely anyone got through the project without help so it is okay to rely on your classmates. I was worried to ask my classmates too many questions at first because I thought this meant I was not grasping the material as well as my peers. Turns out, most groups needed additional help at some point or another as well. Needing help is not an indication that you are not understanding the content we have covered in Mod 1 thus far!
- I learned that I really need to pseudo code before jumping into coding. I found myself starting to code before I really understood what the iteration was asking for and this led to a lot of wasted time and unnecessary confusion.
- In my next project I want to talk to my partner about our pseudo code preferences during the DTR. We can decide if we would rather pseudo code independently before we meet or together before we start coding.