Make connections and start thinking about leadership:
- What roles you tend to fill in groups
- What you do when things get hard
- Your decision making process
- What you value in others and what drives you crazy
#Why
I can explain the difference between function declarations and function expressions. 3
I can explain what the value of this
is in a normal function. 3
I can explain what the value of this
is when called from the context of an object. 3
I can explain how to explicitly set the value of this
in a function. 2
I can explain the difference between call
and apply
. 3
I can explain how the new
keyword changes the way a function behaves.
2
I can explain the implicit steps that happen in my function when I use the new
keyword.
2
I can explain the difference between an object's prototype and the prototype
property on the constructor function.
2
I understand how to place method on a prototype.
Respond to this question in your fork: "What are some of the balances and trade offs between different sorting algoritms?" | |
Steve, did you make us watch this solely because they refer to "JerseyScript"?? | |
- Lexicographical sort: if you just call sort on an array of numbers using js sort, (Array.prototype.sort), it doesn't sort by value but lexicographically. Computer doesn't know they are integers unless we tell it. Need to give (a, b) as args and return (a-b) for ascending sort. | |
-Important characteristics of sorting: stability, runtime analysis, implementation | |
-stable sort maintains relative order with items that are equal | |
-runtime analysis compares time and complexity of sorting algorithms. helps determine best sorting algorithm. Big O is worst case. |
Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)
Step Two: Fork this gist.
Step Three: Respond to this question in your fork: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded). Respond below with your thoughts. Did any of the responsibilities that she lists surprise you? Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?
I had a few good takeaways from this, but it really wasn't that easy for me to separate what she was talking about into the four responsibilities. I don't feel like my IdeaBox in any way split this up, and I'd love to try refactoring it as a practice exercise. I think in Rails apps I had gotten to the point of splitting things up nicely in the models, views, and controllers, and this talk made some points that I could connect to that