This project was building out a desktop and mobile friendly site that allows a user to save "ideas" and then be able to interact with these ideas by favoriting, deleting, and commenting on them. We were also demonstrating the ability to match our design to a comp, build out responsive css with multiple media queries break points, and covered javascript concepts around using more than one class on a project, local storage, and functionality that builds html elements for filtering and displaying what ideas are present on the page.
My approach to working on a team is usally to communicate my strenghts and wekanesses, and to try and assess where best I can fit in, as well as where best we can all utilize our individual strengths. This project was a great example of this model working well, as we early on established a norm of accepting feedback and asking for help. We all had comfort and strength in different areas this project would cover, and were able to lean on one another when out of our comfort zones.
Our biggest technical challenege was how we approached saving "ideas" to local storage. Originally we saved them individually whic presented a whole host of issues aound how to access them indiviually from local storage, which required assigning a key that could then be logically recalled by the system, and then accessing object information from there. And after bouncing ideas off of one another, trial and error, and a few poms, we actually did get things functioning. However the code felt bulky, a little inflexible, and we couldn't see an easy integration of "comments". We didn't want to be storing an obect (comments), on an object(ideas), on and object like structure (local storage). So we ended up deciding to convert our local storage approach to storing an array made up of the idea objects. Finishing a long day with code we knew tecnically worked, we discussed the logic of the refactor, and divided and conquered. The next evening coming we each brought and pitched our refactors, and consulted a mentor to discuss and decide as a team on which we would impliment.
A presonal professional take away, was that group work really can make the entire process faster, more effective, and smoother. Functions should really only do one thing, and parameters are a powerful thing for using functions inside for loops. On the next project I would really like to focus on continues commitment to consistent refactoring at the start of every iteration, and scheduling code reviews at the start of a project.
https://frontend.turing.io/projects/module-1/group-dynamics-reflection.html