Our lesson for today was heavy on scope and protecting the global scope from repeated variable names. They always say your job as a developer will be 90% coming up with names for things. Our activities today were pretty straight forward. We were given lots of functions with improper use of scope and hoisting and had to restructure them so that they worked in the way they were intended.
IIFE’s are used to compartmentalize all the variable names inside a function that will be “immediately invoked” so that you never have to worry about those variable names interfering with your global variables. These kinds of logic rules just make sense to me. If you have two children you wouldn’t name them both the same thing, ever. So don’t do with with your computer babies aka variables.
I’m still waiting on some info on the crash course Bruin and I are leading next week. I’m really hoping the details come along soon. I HATE being unprepared, but I am very excited about the opportunity!
I had a short meeting with the front-end guy and our campus director and was told that I am exceeding expectations and am not a concern for either of them when it comes to finding a job after the cohort. I hope what they say is true! It’s funny how you can never see yourself the way other see you…