Open azra-l opened 2 years ago
CS ID: k4u3u For the last two weeks I worked with my team to formulate and finalize our project idea, isolating key requirements and planning our steps to begin building Festival Fanatic. I also submitted our team project proposal as well as structured and edited our README on the project repository. One of the challenges we faced during this time was deciding between using hard coded data and possibly querying search engines for festival data such as location and ticket price. Within the next two weeks I plan to have my work environment setup and begin working on our two minimal requirements defined in our README with my team.
CS ID: w8u0b Over the past couple of weeks, I also worked with the team to narrow down the scope of the project and derive concrete requirements that we can start implementing. I have also setup a docker-compose.yml and Dockerfile for the development environment setup which integrates natively with VSCode. This mainly installs node and a runnable instance of mongodb with shell access from the terminal right away. This should make the initial stages of development smoother and also ensure everyone is running on the exact same environment across operating systems. For the next 2 weeks, I plan on setting up the boilerplate code for the frontend and backend, finalize a tentative database schema, and implement a couple of scripts that will import a bunch of hardcoded dummy data into the mongodb instance for use to work with during development.
CS ID: d0u1b Over the last 2 weeks, I helped ideate the project and helped brainstorm the potential architecture and tools we needed to get us going. I also researched how to retrieve a user’s liked songs via spotify API and facilitated the refining and discussion around the project requirements and etc. one challenge was trying to write out requirements without the rubric because we’re not sure what we need to include in our project. For the next 2 weeks, I’m going to look at how we should use the spotify api to our advantage and decide what data we need to store for our use cases
CS ID: i2w2b Over the past 2 weeks, I worked with my teammates to finalize our project idea, define our requirements and sketch prototypes for the key actions of our app. A challenge we ran into was deciding which data we would have to store so the app could display festival results for the majority of Spotify users, and how to deal with cases of users with niche music preferences. Over the coming two weeks, I will set up my local dev environment and start working with my teammates on building React components for our festival cards and login screen.