1 array.each
This will be a smaller conceptualization of render compared to reroute in the world of Ruby on Rails.
It is a big moment to get to the technical interview stage; it is exciting and nerve wracking at the same time. The initial step after getting the question is to think things out and figure out how to solve the question. Then, after communicating the thought process and finally getting the code to solve the problem, is that it? Nope, the next question to ask yourself is, “is this the most efficient answer?” We now must consider Big O notation.
Recently, I have been tasked with creating a slot machine web app using react and redux for the front end. Before starting, I would like to blog out the planning process and layout any questions I may have in the future. My planning process goes as followed: function (what is the goal of the app), breakdown and structure (folder structure and architecture). Along the way, I also like to write out possible challenges I will come across.
For my recent technical interview and a few coding questions I have been working on, I realize that I am taking the same approach. My way of thinking has been to create a set of rules to follow with a bunch of while loops and if statements. Although, not often the most efficient, it is effective and has a few benefits.