Truthfully when starting this program this is what I expected all coding to look like. Every step through this journey gets more complex and shows me just how much you can and must do to build a high functioning application. As far as building functionality, JavaScript seems to be in a class of its own. Although this phase of the program made me feel like being back at day one; it really gave me insight on how other apps are made and what it takes to make them great for a user to navigate them.
My JS app is all about the most beautiful beaches in the world. The backend of my project was pretty simple to get done with my prior rails knowledge. Even with the knowledge of being able to use scaffold this time around, it showed me exactly why I wasn't allowed to use it previously. Additionally it sped the process of building my backend up so that I could focus on the frontend JavaScript thoroughly. I created an api with seeded data of just a few of the beaches the world has to offer. This list has the options to add to, delete, and edit. Each beach also has a comment section where people can come together to talk about and share their experiences on said beach.
Each function contained a lot more code than a rails method. Most of them included arrow functions in addition to the backend methods. The logic to show different errors linked back to the method that housed the specific error. It seemed to be almost like everything in the index.html file was like building the layout in rails. In addition the index.js file contained all the views that would have had their own folder. The logic of how to handle each method in each function combined with the event listeners to be able to use them.
All in all with my project build I know that I've only hit the tip of the iceberg and that there's so much more to learn in this new language.
Top comments (0)