As a group, create a project that integrates front-end knowledge as well as back-end knowledge
This Project's goal was to create an app that uses both front-end technology as well as a back-end technology giving us a finished product of a full-stack application
Project 2 - Carbon Watchers
For our second project our group decided to build off of Ryan's project 1. With access to our site, you will have the ability to see the total carbon emissions for many different avenues, as well as create an account and put in your specific information for your personal calculated carbon emissions.
We originally decided to break up the roles into front-end and back-end. We had assigned Ryan and Kelley to worry about the back-end and Keissa and Jacek to worry about the front-end. Luckily for our group Ryan is a very knowledgeable classmate and he ended up really helping each of us out on all different points.
We ran into a facet of challenges throughout this project. We started with a really robust code base that was strictly front-end. We thought this might help us out in the code writing process but it actually seemed to do the opposite. It was a massive hurdle for us to be able to get the front end organized in a way that would communicate efficently to the back-end that we had added on. We also had the challenge of breaking the original HTML up and seperating it into functional handlebars. All in all we made it work and ended up with a functioning app. This isnt to say that if we could start from scratch we would have cleaned up our code much more and refractored more where we could.
The initial set up of the actual database for the user information was very quick to get functioning on its own through insomnia core, however getting it to function on the page itself with the front-end posed a whole other set of challenges. Ryan was able to come up with the math and code to be able to succesfully track a single persons carbon emissions by their inputed information. This project taught us a lot of troubleshooting and problem solving and how to get around things when you already have a code base in place. All in all it was a success to get it WORKING!