![]() ![]() The mindset.Īfter understanding this concept, actually thinking through problems in an if.else or if.then aspect, really helps solve any challenges in JavaScript. Being aware that it is a functional language, I quickly learned the power of the if.else thought process. I am unsure of how to put this exactly, but in essence, JavaScript is the only language I've worked with, thus far. Before that, I had never given a thought to what data I needed exactly. Some small minor things that I never considered, in comparison to using a free, easy to use API that throws you a JSON object right off the bat. I learned how important it is to break down each step of the goal you're trying to achieve. While the back-end developers in our group had already taken the front-end curriculum, and could understand what we were attempting to do - it was definitely difficult understanding them! This definitely stood out as a challenge, when faced with speaking to data science and back-end developers. I found this so neat, and was a nice new nugget to take away! Learning to speak other developer's language Private Routes in React Router allowed us to prevent the dashboard of the application being available to a user without an account to our application. As someone who never gave URLs much thought, I never considered the idea to navigate to a different URL ( that you may not have access to!) Standard Routesįor some, this may be obvious, but I found this concept extremely interesting. So many questions come into play, and without effective communication, you're left in the dust! Be sure to inform others of any large changes, mistakes, issues, or conflicts. Who is available at certain times? (Considering sometimes we get paired with students overseas).Who is handling the majority of the merge conflicts?.Which person is building which feature?.When paired with such a large group of individuals, I quickly realized the importance of communication. While it was only 4 days, I feel I learned a lot during that time, so here is the general breakdown: Team Communication private routes, and ultimately my first implementation of React in a project environment! What I learned Overall it was a simple idea, but really fun implementation of React. What provided us with more experience with React Router, was providing each card with the option to save that song to a " Saved Songs" tab, where we displayed every song the user saved - similar to a playlist.įrom this saved songs tab, we provided the option to either view the song (in the expanded song view, featuring all of the information covered above), or remove it from the playlist tab altogether. Giving the user the ability to discover new music they may have not heard before! We then displayed that data on a card along with the original song information. The neat part was the data science developers were able to use a model to provide songs that were similar to your selected song's genre. A snippet of the song rendered from the Spotify API.A chart displaying the data attributes of each song.We used this to find songs that matched the user's input, and allowed them to select an option to view extended information about that song. We then implemented a search bar, to filter through the large sum of songs. We were tasked with grabbing data from the back-end developers, and rendering it on our application that we created. Essentially our project was a " song suggester".ĭata science provided the back-end Java developers with raw data containing 130k+ songs, and attributes for each song such as: energy, loudness, danceability, etc. The project was an awesome idea, it taught me a lot about React, React Router, and User log-in. Data Science to mold the data for the back-end developers x 3.Back-End Java Developers to provide access to the data x 2.Front-End React Developers to build the application x 3.Web UI Developer for a landing page x 1.Our team was rather large for the project, however, we definitely made it work! Starting from beginning to end, we had: Here's what went down during week 8! My Team We are given a 4 days, Monday through Thursday evening, to build a project chosen from a list of provided ideas. Hopefully giving you a solid insight of what a week at Lambda could look like! This past week there was not any new curriculum taught as it was project week, or as they call it, build week. For those of you who are unfamiliar with these posts, I have a weekly post walking everyone through my week at the Lambda Bootcamp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |