Working within technology, be it design or development, is a fast-paced world. These fields are constantly moving and changing, breaking down barriers and evolving to new possibilities. This can be daunting and scary to some, but can instead excite and energize others. This world of technology needs people who are “life-long learners”, those people who are motivated by a fast paced and ever-changing career field and are willing to put in the work to further themselves and others to push the status quo forwards.
Using Javascript for your frontend single page apps (SPA’s) can lead to highly interactive and very friendly user experiences. It can greatly reduce or deminish the need for browsers to send requests to a server, and in turn speed up the usage and flow of your applications. On top of that, the use of Javascript is fun! It can open up the doors to a great many features over those of HTML and CSS.
When coding in Javascript, Hoisting is an important topic to understand when thinking about scope and order of operations in Javascript. But when the topic was first discussed in the JS Learn Tutorials, I was VERY lost. “Hoist WAT!?” - I said to myself.
We have all been there. Working on a problem or adding a fun new feature into our projects, and you cant decide where to properly add the code we want to implement. Rails, though magical, should be implemented properly to remain as efficient, developer friendly, and least repetitive as possible by being DRY while using MVC pattern principals. When programming functionality into your rails app it is important to know what kind of logic should go where.
When it comes to creating your Rails Final Project, the possibilities seem endless. Where do you start, what features should you impliment, and what kind of additional improvements can you make near the end.