I was recently asked during a technical interview a question regarding how databases worked in the context of finding records with queries. Though I talked about primary and foreign keys, the term I really needed to needed to use was index. I did a little research using the book Practical SQL by Anthony DeBarros and learned a couple ideas about databases and indexes.
I was interviewing for a Ruby on Rails roles and asked to think about how to speed up page loads when rendering long lists in the view. In this situation the index view rendered a list that included information from objects accessed with a belongs_to relationship. There are multiple ways to get this information on the page. I will show two ways that differ in their speed due to the number of calls to the database. I’ve changed the example from what was in the interview.
The past couple of months I have collaborated on a project started by another Flatiron Grad. I found his posting on our slack channel asking for collaboration for a Ruby on Rails and React web application. Having just graduated from the online, self-paced program, I was excited to jump into a project with another developer since up to that point all my experience programming was solo. Adam had built most of the Rails API only backend including testing and authentication. My task was to build the React frontend including sign up and login features. We are almost ready to deploy! There are many things I have learned through this experience. In this post I will share a few lessons specific to collaborating using version control versus using it solo.
These notes are the last of the lessons for Wes Bos’s fabulous Javascript30 course.
Over half done! My notes from Wes Bos’s Javascript30 class that is fun, high quality, and efficient in presenting relevant and useful concepts. If you want to practice your Vanilla JS, I highly recommend it.