////////////////////////////////////////////////////////////////////* Creating an Immediately Invoked Function Expression - Step by Step */var newScope = function(a, b, c){
var a, b, c; // these are local to this function. return a + b + c;
};
newScope(1,1,1); /* 3 ---> Variables a, b, c are contained inside the function's scope. They can not be
accessed from the global scope. *//* A different way to get the function to run is to create it without a name and than type in the
syntax so it runs immediately. Since the function does not have a name I can NOT call it like newScope(); *//* (1) Create a function without a name: */function(a, b, c){
var a, b, c; // these are local to this function.return a+b+c;
}
/* (2) Put parenthesis around that function: */
(function(a, b, c){
var a, b, c; //these are local to this fucntion.return a+b+c;
}) /* ---> these parenthesis do NOT call the function. They are acting like parenthesis in a math problem, such
that what is inside the parenthesis get evaluated. They evaluate to a function object. *//* (3) Since the parenthesis in 2 above evaluate to a function object, I can now call the function by putting
another set of parenthesis at the end. */
(function(a, b, c){
var a, b, c; //these are local to this fucntion.return a+b+c;
})(); /* ---> This last pair of parenthesis will call the function. They are function execution parenthesis
meaning they can take arguments like any other function call.*//* This is called an Immediately Invoked Function Expression. It is how I create a private scope. Since
it does not have a name there is no way for a name collision to happen with another script/function.
Also, the variables are local/inside the function's scope so it will not leak out into the global space. */
(function(a, b, c){
var a, b, c; //these are local to this fucntion.return a+b+c;
})();
///////////////////////////////////////////////////////////////////

I'll keep that in mind. Thanks for the help @crisberrios. Honestly, if we don't have to worry about 4 level deep arrays, I say take out that exercise. Stay concentrated on what we really need to know to get a job. Just my opinion.

well... bootcamps have to mantain a balance between proper learning and fast learning. I'm leaning towards proper learning so I value the bonfires. Of course, they can be revised and the difficulty adjusted.

since I'm an RPG games fan, I envision having multiple masters paths after the basic curriculum

Yeah, I agree about the proper learning. Fast learning in programming usually doesn't work that well. But, a bootcamp is here to prepare us for a first job. I am thinking knowing how to solve 4 level deep arrays is usually not an interview question.

Just watched that philip roberts video...well mostly done. watching his interactive tool run (Loupe), the event loop to me is a way of managing tasks & interruptions. It's like working in the ER. There is only one of me, but there are many things going on at once because I task others to take care of small bits. When a piece of information is ready (reviewing lab tests), the nurse will wait till I am "interruptable" (ie my call stack is empty) then let me know tests are back (or patient is in pain or whatever). Cool stuff

I see an opportunity for a parallel learning track for bonfires, one in which you know the method (or one of 2 or 3) and need to implement a new creative use of it. Get to know the methods and make something happen. Then the next step could be the progressively harder bonfires.

Hey all! I'm on the "Where art thou" bonfire, and I'm feeling pretty lost as to where to start. I have tried searching through it as an array, but I don't know how to search for a specefic key within that...does anyone have any tips on what direction I should be going? Meanwhile I'm googling and reading :)