I recently completed my mock technical interview and was faced with answering rapid fire questions about common programming/JavaScript terms and discovered that I prattle when giving descriptions (which takes away time from the code challenges where one would want more time to work with). Part of the feedback from my interview was to come up with concise (quick) definitions/descriptions for commonly asked about terms. As practice, and for posterity, I’ve put together a list of definitions (with resource links) here. This is a growing list that I’ll continue to add to as I encounter other terms during interviews.
Yesterday was the Global Day of Coderetreat.
Almost to the finish line! I’ve completed my React-Redux portfolio project - just need to get through my assessment and then it is graduation time!
Unlike the Rails Project where I felt like I had a good grasp on what I needed to build to meet the project requirements, the JS project had me stumped. I didn’t know where to begin and didn’t fully understand the requirements that were provided. This probably had a lot to do with how much I struggled with the JavaScript section starting with the AJAX chapters. The curriculum felt a bit choppy starting at that point and I had a really hard time understanding how all the different pieces and parts were supposed to fit together. Things cleared up a bit for me after watching the AJAX videos that Avi recorded as well as after going to a few of the AJAX study groups (well worth the time! – thank you, Seth!).
For my Ruby on Rails project I had decided to build a Money Manager app since it would lend itself well to scope methods (such as total expenses by category or all expenses from today or this month). I started the project by sketching out my models and their relations ships on a piece of paper (Users have many Expenses and many Categories through expenses, Expenses belong to Category and User). I found that diagrams are way easier to wrap my head around than just writing down the relationships themselves. Then I wrote out some notes on some of the things the application would need to do in order to meet the project requirements (such as validations, scope methods, error display, nested resources, etc).