Reading Docs, Challenging Myself and a Little Interview Prep

This week, I’m rounding out my JavaScript 211 course and have hit some good milestones in my learning to program journey. Yes, I continue to struggle with how to write good unit tests, especially for API calls, but this is just one topic that I will continue to work through outside of classes.

This week I spent a good amount of time reading documentation on Lodash, a JavaScript library that uses underscore notation (._).

This was somewhat challenging, since this learning was one of the first times I was learning a library only from documentation, rather than having more guidance. However, the struggle, a lot of errors and finally some unit testing, I feel proud of being able to write a few functions using this library and knowing that I could be able to learn something independently (well, with some help from classmates) is another step towards becoming a developer.

Macbook with post it notes stating phrases, “code, debug, learn, sleep, repeat”
Image from user ID# 15548331 on Pixabay

Some More Intro Developer Interview Prep:

Explain Function.prototype.bind()

In JavaScript, the function bind() creates a new function, that has its this keyword set to the supplied value. This uses a given sequence of arguments preceding any provided when the new function is called.

From: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_objects/Function/bind

What is event bubbling?

Event bubbling refers to the order event handlers are called when one element is nested inside a second element. In event bubbling, both elements have registered a listener for the same event (e.g., “onClick”).

What’s the difference between the window load event and document DOMContentLoaded event?

The DOMContentLoaded event fires when parsing of the current page is complete.

The load event fires when all files have finished loading from all resources (e.g., images, ads, videos).

Describe the call stack.

The call stack is the data structure which stores information about the active routines and subroutines of a program. It’s essentially the list of activities (often functions- including implicit functions) that are firing and the data being stored as a result. The call stack is useful in debugging since it is essentially a list of all the active functions that have been called to get to the current point of execution. The call stack includes an entry for each function called, as well as which line of code will be returned to when the function returns.

I hope this helps anyone who is pushing themselves further in their coding journey to feel a little less isolated. Remember, celebrate the little wins and that even the most senior developer (or genius) had to start with the same “hello world”!

Your friend in code,

Rachel

I am an avid adventurer taking readers on my latest journey in learning to code. Let’s get started from 0 experience to programmer!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store