My latest update to CORE, a course creation rails application, was made to fit requirments where JavaScript, JSon, JQuery, and the serializing of data where to be used. This was exciting because I would now be making my application more dynamic and modern, it would come with challenges but I was eager to get started. Quickly challenges hit me, especially because I wanted to do things that I hadn’t even learned yet or didn’t have such a strong grasp on. The most challenging being the creation of a next button that would allow the user to go through the courses without a page refresh. I quickly realized there weren’t many thorough guides on building a JavaScript function that accomplished this task. With the help of my instructurs and scaling back I was able to accomplish this goal. With this new information, I thought it would be good to give other people my outline on how I created the next button using JavaScript and Json data.
For my Rails application I decided to build an app for people who would like to build courses pertaining to the mind, body, and soul. Mental health is an important thing to me and what better way to show it than building an application around it. This project was more challenging than the last two because of how I originally went about building it. Although, challenging I learned some very valuable lessons that I can take with me for my future project builds. Below are some “gems” that I wish I had followed before building CORE
As someone who has followed along with the tech community before joining Flatiron School, it’s not unlikely that I became privy to a couple tech phrases. One of them being called the “imposter syndrome”, this phrase sounds just like how it would be defined. Someone who has entered a community and feels as if they don’t belong. Don’t get me wrong Flatiron has been one of the most inclusive tech communties i’ve ever participated in.
The undertaking of a CLI is something that I thought would be nearly impossible. Even though I’ve been learning all of this amazing information from Flatiron, the power of the blank screen definitely intimidated me. This is where I had to realize that the code DOESN’T have to be perfect the first time around. It may seem like you’re stepping into the abyss but once the wheels start turning in your brain then no one can stop you from building something amazing. So, how did I implement this golden rule? I did it by following the steps below.