I have got to admit when I first dived into this course I would not have had such a solid understanding of javascript as I would have now. While building some of my projects especially when I was using rails as an api I discovered a marvelous feature javascript provides to its developers, hoisting. Hoisting is in javascript refers to how and where we declare our javascript variables, it allows variables to declared after it has been used, in other words a variable can be used before it is declared. When I first saw this topic I was really confused, after taking some to appreciate it I began to find it very useful. With Javascript hoisting we can move all javascript variable and function declarations to the top of the current scope which makes it is easy to reassign variables. This javascript fundamental came in handy when I was trying to build bigger javascript applications that required me to call javascript functions before they are actually declared.
Over the last six months of this program I immersed myself to new new programming languages and topics I never would have known if I had not attended the Flatiron School. My hard work and self-determination paid off when I was built my final portfolio project which is a react-redux application with a ruby on rails api. React JS and Redux are two very new concepts to me, after taking the time to embrace them and incorporate them into my codebase I began to appreciate them.
My Javascript and Rails project aims to mimick how a user interacts with an online job board, in other words, it has features and functions you would find when looking for a new job. My application allows users to add a job, delete a job and search for a job.
Over the course of this past few weeks I got the chance to create an end-to-end web application with Ruby on Rails web development framework. Ruby on Rails makes much more fun and easy to develop web applications as it provides users with a variety of tools to make their apps more practical, requiring less code and less time debugging. When I first saw this framework, I was very concerned about defining all of my http verbs and resource requests, rails made it very easy for me to make distinctions between them and create unique end-user experiences. By making it easy to define http verbs, I was able to create an elegant user experience by creating log-in functionalities and behaviours I otherwise could not have done without ruby on rails.
One hour of code per day can save the world.