Alison Nooner

finalPrep/README.md

@@ -2,13 +2,13 @@
 Congrats on making it to the Mod 0 Final Prep! Complete the final exercises below and be sure to carefully follow the Pull Request steps to submit your work!
 
 ### Final Technical Prep
-You've learned a ton about some of the core foundations of Javascript! Show us how far you've come by completing the following exercises! You will be using your work from these exercises in your first day of Mod 1! 
+You've learned a ton about some of the core foundations of Javascript! Show us how far you've come by completing the following exercises! You will be using your work from these exercises in your first day of Mod 1!
 
 - [ ] Complete the [Mod Zero Hero Challenge](./modZeroHero.js)
-- [ ] Complete the [Annotation Challenge](./annotations.js) 
+- [ ] Complete the [Annotation Challenge](./annotations.js)
 
 ### Refactor Previous Work
-You've learned A LOT over the last few weeks as it relates to technical content - chances are, you probably have some code from your previous exercises that is either sloppy, incorrect, poorly named, etc. Before starting Mod 1, we want you to `refactor` your code - which is the process of adjusting or improving your code for readability and accuracy. 
+You've learned A LOT over the last few weeks as it relates to technical content - chances are, you probably have some code from your previous exercises that is either sloppy, incorrect, poorly named, etc. Before starting Mod 1, we want you to `refactor` your code - which is the process of adjusting or improving your code for readability and accuracy.
 
 Some things to consider as you refactor include...
 - Are my variable names easy to understand/convey the data type they are assigned to?
@@ -18,37 +18,41 @@ Some things to consider as you refactor include...
 
 Take your time as you go back and refactor your exercises from each section. We've included a handy checklist for you to go through below.
 
-- [ ] I have refactored my `section1` exercises to the best of my ability
-- [ ] I have refactored my `section2` exercises to the best of my ability
-- [ ] I have refactored my `section3` exercises to the best of my ability
-- [ ] I have refactored my `section4` exercises to the best of my ability
+- [x] I have refactored my `section1` exercises to the best of my ability
+- [x] I have refactored my `section2` exercises to the best of my ability
+- [x] I have refactored my `section3` exercises to the best of my ability
+- [x] I have refactored my `section4` exercises to the best of my ability
 
 ### Time Management Prep
 In Mod 0 you've learned about different techniques for managing your time at Turing. Please create a calendar for your **first 3 weeks of Mod 1**. Feel free to make your calendar fit your style, but we suggest that your calendar should include the following:
-- [ ] Standard M1 class schedule (see M1 calendar [here](https://frontend.turing.io/today/))
-- [ ] Study/Project work time
-- [ ] Health + Wellness
+- [x] Standard M1 class schedule (see M1 calendar [here](https://frontend.turing.io/today/))
+- [x] Study/Project work time
+- [x] Health + Wellness
 
 When you are finished, add screenshots of your calendar so we can provide feedback if needed!
 
-- `Add Week 1 Screenshot Here`
-- `Add Week 2 Screenshot Here`
-- `Add Week 3 Screenshot Here`
+<img width="1147" alt="Screen Shot 2021-10-30 at 1 30 16 PM" src="https://user-images.githubusercontent.com/92279624/139554832-7baebc77-ae87-4df6-a96b-c30290f555b1.png">
+<img width="1147" alt="Screen Shot 2021-10-30 at 1 30 25 PM" src="https://user-images.githubusercontent.com/92279624/139554811-364e60ab-d77b-4b46-8e67-d9f02d064b40.png">
+<img width="1147" alt="Screen Shot 2021-10-30 at 1 30 31 PM" src="https://user-images.githubusercontent.com/92279624/139554576-24a7a6cf-bfd9-4fba-ad18-80bab2ba99d0.png">
 
 ### Mentorship Prep
 Mentorship is an integral part of the Turing experience and will help jumpstart your technical career. In order to get your mentor relationship started on the right foot, please complete the following deliverables:
-- [ ] Complete the [Mentorship DTR Prep](https://gist.github.com/ericweissman/51965bdcbf42970d43d817818bfaef3c)
-  - [ ] Add link to your gist here: 
+- [x] Complete the [Mentorship DTR Prep](https://gist.github.com/ericweissman/51965bdcbf42970d43d817818bfaef3c)
+  - [x] Add link to your gist here:
+https://gist.github.com/AliNooner/92521623e6747d088bcbe44b1771198b
 
 ### Lesson Prep
 You've learned a lot about how to take strong notes during Mod 0. Show us your skills while you learn how to pre-teach content for your first lesson in Mod 1!
-- [ ] Complete the [Pre Teaching Practice exercise](https://gist.github.com/ericweissman/0036e8fe272c02bd6d4bb14f42fd2f79) gist
-  - [ ] Add a link to your gist here:
+- [x] Complete the [Pre Teaching Practice exercise](https://gist.github.com/ericweissman/0036e8fe272c02bd6d4bb14f42fd2f79) gist
+  - [x] Add a link to your gist here:
+https://gist.github.com/AliNooner/b0bd440a8117652b209a8b83cad5d46f
 
 ### Group Work Prep
 As part of Turing's project-based learning approach, you will often be working in pairs or larger groups. In order to set yourself (and your team) up for success, it is important to ensure you are prepared to be an equitable contributor and teammate.
-- [ ] Complete the [DTR Guiding Questions](https://gist.github.com/ericweissman/c56f3a98cdce761808c21d498a52f5c6)
-  - [ ] Add a link to your gist here: 
+- [x] Complete the [DTR Guiding Questions](https://gist.github.com/ericweissman/c56f3a98cdce761808c21d498a52f5c6)
+  - [x] Add a link to your gist here:
+https://gist.github.com/AliNooner/996aa77a70d7935a29c78ecd6ce2e06a
+
 
 ## All Done? How to Submit your M1 Prework
 When you have completed *ALL* the activities described above, follow the steps below to submit your technical prework.
@@ -87,4 +91,3 @@ What is your plan and how are you going to hold yourself to it? Specifically...
 
 ## Extensions
 Check out our thoughts on [extension activities](https://mod0.turing.io/prework/extensions) if you find yourself with some extra time before starting Mod 1!
-

finalPrep/annotations.js

@@ -3,40 +3,61 @@
 
 //Build a Bear
 function buildABear(name, age, fur, clothes, specialPower) {
+  // define the greeting variable which will return "Hey partner! My name is (name varilable) - will you be my friend?"
   var greeting = `Hey partner! My name is ${name} - will you be my friend?!`;
+  //define the demographics variable that will include the name and age
   var demographics = [name, age];
+  // define the powerSaying variable that will concatenate with specialPower
   var powerSaying = "Did you know that I can " + specialPower + " ?";
+  // definte the builtBear Object
   var builtBear = {
+  // defines key:pair basic information as demographics
     basicInfo: demographics,
+  // defines key:pair clthes as clothes
     clothes: clothes,
+  // defines key:pair exterior as fur
     exterior: fur,
+  // defines key:pair cost as 49.99
     cost: 49.99,
+  // defines key:pair sayings as greeting, powerSaying and "Goodnight my friend!"
     sayings: [greeting, powerSaying, "Goodnight my friend!"],
+  // defines key:pair as true
     isCuddly: true,
   };
-
+ // will return the information stored in the builtBear object
   return builtBear
 }
-
+ // this will build a bear named Fluffy who is 4 years old with brown fur. They will be wearing pants, jorts and a tanktop
+ // their special power will be to give you nightmares
 buildABear('Fluffy', 4, 'brown', ['pants', 'jorts', 'tanktop'], 'give you nightmares');
+// this will build a bear named Sleepy who is 2 years old with purple fur. They will be wearing pajamas and a sleeping caption
+// their special power will be sleeping in
 buildABear('Sleepy', 2, 'purple', ['pajamas', 'sleeping cap'], 'sleeping in');
 
 
 
 //FizzBuzz
 function fizzBuzz(num1, num2, range) {
+// each item stored in fizz buzz will be returned, starting at index 0, moving on to index 1
+// this process will repeat with each item until it reaches range and fizz buzz will stop
   for (var i = 0; i <= range; i++) {
+// if num1 and num2 are not even it will log "fizz buzz"
     if (i % num1 === 0 && i % num2 === 0) {
       console.log('fizzbuzz');
+// will return "fizz" if the above argument is true, if not it will continue running the code
     } else if (i % num1 === 0) {
       console.log('fizz');
+// will return "buzz" if the above argument is true, if not it will continue running the code
     } else if (i % num2 === 0) {
       console.log('buzz');
+// if all three above are false, it will return the value of i
     } else {
       console.log(i);
     }
   }
 }
 
+// this will return "fizz"
 fizzBuzz(3, 5, 100);
-fizzbuzz(5, 8, 400);
+// this will return "buzz"
+fizzbuzz(5, 8, 400);

finalPrep/modZeroHero.js

@@ -1,41 +1,59 @@
 // Challenge - See if you can follow the instructions and complete the exercise in under 30 minutes!
 
 // Declare two variables - heroName AND specialAbility - set to strings
-
+var heroName = "Cal the Calmer"
+var specialAbility = "Chi Manipulation"
 // Declare two variables - greeting AND catchphrase
 //   greeting should be assigned to a string that uses concatenation to include the heroName
 //   catchphrase should be assigned to a string that uses interpolation to include the specialAbility
-
+var greeting = "I am" + heroName + "and I'm here to bring you down a notch!";
+var catchphrase = "$(specialAbility) for any situation!";
 // Declare two variables - power AND energy - set to integers
-
+var power = 1000;
+var energy = 10;
 // Declare two variables - fullPower AND fullEnergy
 //   fullPower should multiply your current power by 500
 //   fullEnergy should add 150 to your current energy
-
+var fullPower = (power * 500);
+var energy = (energy + 150);
 // Declare two variables - isHuman and identityConcealed - assigned to booleans
-
+var isHuman = true;
+var identityConcealed = false;
 
 // Declare two variables - archEnemies AND sidekicks
 //   archEnemies should be an array of at least 3 different enemy strings
 //   sidekicks should be an array of at least 3 different sidekick strings
-
+var archEnemies = ["Karen the Complicator", "Undies in a Bundle", "Steve the Stressman"];
+var sidekicks = ["Chilled out Charlie", "Relaxing Rex", "Slow Down Sally"];
 // Print the first sidekick to your console
-
+console.log(sidekicks[0]);
 // Print the last archEnemy to the console
-
+console.log(archEnemy[2]);
 // Write some code to add a new archEnemy to the archEnemies array
-
+archEnemies.push("Tense Travis");
 // Print the archEnemies array to console to ensure you added a new archEnemy
-
+console.log(archEnemies);
 // Remove the first sidekick from the sidekicks array
-
+sidekicks.shift();
 // Print the sidekicks array to console to ensure you added a new sidekick
-
+console.log(sidekicks);
 // Create a function called assessSituation that takes three arguments - dangerLevel, saveTheDay, badExcuse
 //   - dangerLevel should be an integer
-//   - saveTheDay should be a string a hero would say once they save the day 
+//   - saveTheDay should be a string a hero would say once they save the day
 //   - badExcuse should be a string a hero would say if they are too afraid of the dangerLevel
-
+var dangerLevel = 20;
+var saveTheDay = "I am here to save the day!";
+var badExcuse = "I just remembered I have cookies in the oven..."
+
+function assessSituation (dangerLevel, saveTheDay, badExcuse){
+  if (dangerLevel > 50){
+    console.log(badExcuse);
+  } else if (dangerLevel >=10 && dangerLevel <=50);
+    console.log(saveTheDay);
+  } else {
+    console.log("Meh. Hard pass.");
+  }
+]
 // Your function should include an if/else statement that meets the following criteria
 //   - Danger levels that are above 50 are too scary for your hero. Any danger level that is above 50 should result in printing the badExcuse to the console
 //   - Anything dangerLevel that is between 10 and 50 should result in printing the saveTheDay string to the console
@@ -48,37 +66,81 @@ var excuse = 'I think I forgot to lock up my 1992 Toyota Coralla. Be right back.
 //assessSituation(21, announcement, excuse) > should print - 'Never fear, the Courageous Curly Bracket is here!'
 //assessSituation(3, announcement, excuse) > should print - "Meh. Hard pass."
 
+assessSituation(99, announcement, excuse);
+assessSituation(21, announcement, excuse);
+assessSituation(3, announcement, excuse);
+
 // Declare a new variable - scaryMonster - assigned to an Object with the following key/values
 //   - name (string)
 //   - smell (string)
 //   - weight (integer)
 //   - citiesDestroyed (array)
 //   - luckyNumbers (array)
 //   - address (object with following key/values: number , street , state, zip)
-
+var scaryMonster = {
+  name: "Claws McGraws",
+  smell: "Old cheese",
+  weight: 375,
+  citiesDestroyed: ["Tuscon", "Madison", "Las Vegas", "Reno"],
+  luckyNumbers: [13, 9, 6],
+  address: {
+    number: 1396,
+    street: "Scary Street",
+    state: "Reno",
+    zip: 89433;
+  }
+}
 
 // Create a new class called SuperHero
 // - Your class should have the following DYNAMIC values
-//   - name 
+//   - name
 //   - superpower
-//   - age 
+//   - age
 // - Your class should have the following STATIC values
 //   - archNemesis, assigned to "The Syntax Error"
 //   - powerLevel = 100
-//   - energyLevel = 50 
-
+//   - energyLevel = 50
+var SuperHero {
+  constructor(name, superPower, age) {
+    this.name = name;
+    this.superPower = superPower;
+    this.age = age;
+    this.archNemesis = "Tacky Thomas";
+    this.powerLevel = 100;
+    this.energyLevel = 50;
+  }
+}
 // - Create the following class methods
 //   - sayName, should print the hero's name to the console
 //   - maximizeEnergy, should update the energyLevel to 1000
 //   - gainPower, should take an argument of a number and INCREASE the powerLevel by that number
 
+sayName() {
+  console.log(this.name);
+}
+
+maximizeEnergy() {
+  this.energyLevel = 1000;
+}
+
+gainPower(number) {
+  this.powerLevel = this.powerLevel + number;
+}
 // - Create 2 instances of your SuperHero class
 
+var heroOne = new SuperHero ("Nicole", "Telekenesis"; 29);
+var heroTwo = new SuperHero ("Lauren", "Teleporation"; 30);
 
 // Reflection
 // What parts were most difficult about this exerise?
-
+This exercise was great because it included all, if not most, of what we've covered in our prework.
+The most difficult part was just remembering everything and how each piece fits in and making sure
+all of the syntax was being used correctly.
 // What parts felt most comfortable to you?
-
+I felt comfortable in that I really feel like I understsand these concepts. When I couldn't exactly
+remember something off the top of my head, I knew where to look back in my prework exercises for help.
 // What skills do you need to continue to practice before starting Mod 1?
-
+I am going to go over EVERYTHING until Mod 1 starts; my notes from class, from our homeworks and from the prework.
+I am going to re-do everything from scratch and make sure I have these concepts locked down before 11/29.
+I could not be more excited to continue to feel more comfortable with everything I've learned and to continue
+building on this knowledge.

section1/README.md

@@ -12,7 +12,7 @@ Section 1 is estimated to take a total of 6-10 hours to complete. Part C is the
 
 If you've talked to any alum or near-alum of Turing, one thing they likely shared is "Turing teaches you how to learn". For creators of tech, the learning never ends. Not after graduating a program, not after 20 years of experience. We will provide more support as you are starting out, then release some of that support so you are equipped to learn on your own once you graduate. While we provide more support at the beginning, we also intentionally support you in building skills and habits that will help you do that successfully.
 
-One of those pieces is in how developers approach vocabulary. Knowing technical vocabulary will allow you to get more out of reading doucmentation and tutorials, and will allow you to communicate well with teams and ask good questions when you need help. Each section of your pre-work (and each lesson once you start Mod 1) will start with a vocabulary section. We don't always give you the definitions - this is intentional. You will create your own definition after having several opportunities to read definitions and see examples.
+One of those pieces is in how developers approach vocabulary. Knowing technical vocabulary will allow you to get more out of reading documentation and tutorials, and will allow you to communicate well with teams and ask good questions when you need help. Each section of your pre-work (and each lesson once you start Mod 1) will start with a vocabulary section. We don't always give you the definitions - this is intentional. You will create your own definition after having several opportunities to read definitions and see examples.
 
 Here's what we ask you do:
 - Find a special spot in your notebook for vocabulary and JavaScript reserved keywords. Mark it with a post-it or bookmark, so it's easy to find and come back to
@@ -41,7 +41,7 @@ Here's what we ask you do:
 
 ## Part A Super Learner Habits
 
-Read [this article](https://pubs.ppai.org/pc-today/six-habits-of-super-learners/) about the habits of Super Learners. Reflect on this - what do you already do? Does this make you want to do anything new or different as you beginthis learning journey? Jot down your notes now, and we will ask you to share some reflections with your small group at the end of this section.
+Read [this article](https://pubs.ppai.org/pc-today/six-habits-of-super-learners/) about the habits of Super Learners. Reflect on this - what do you already do? Does this make you want to do anything new or different as you begin this learning journey? Jot down your notes now, and we will ask you to share some reflections with your small group at the end of this section.
 
 ## Part B Terminal
 
@@ -213,7 +213,7 @@ The last String in the previous example is interpreted as a String even though i
 
 The **Boolean** data types evaluates to one of two values: `true` or `false`. This data type can seem a little abstract, but Booleans are very helpful in helping us determine which script should run.
 
-There are many cases in whie we want to ask a program a question, such as "Does the username and password typed in match what we have in the database?". This is a yes/no question. We will ask the program the question in a way that it will respond with `true` or `false`. Here are a couple of examples:
+There are many cases in which we want to ask a program a question, such as "Does the username and password typed in match what we have in the database?". This is a yes/no question. We will ask the program the question in a way that it will respond with `true` or `false`. Here are a couple of examples:
 
 _These are all examples of statements that evaulate to a `Boolean` data type in JavaScript:_
 
@@ -310,13 +310,13 @@ Let's take a look at why that resulted in a string. We have a variable called `s
 > 👩‍💻 PAUSE here, and complete the exercises in `concatenation.js`
 
 ### Interpolation
-In addition to concatenation, you may also have seen interpolation used to inject values into strings! One benefit of interpolation is that it can be easier to read in longer strings and don't require concatenating separate strings together. 
+In addition to concatenation, you may also have seen interpolation used to inject values into strings! One benefit of interpolation is that it can be easier to read in longer strings and don't require concatenating separate strings together.
 
 Interpolation requires slightly different syntax to inject values into a string. Follow the below formula to utilize interpolation:
 1. Use the backtick (same key as the `~`, or the key to the left of the `1` key on a mac) to wrap your entire string
 2. Any values that you want to add in, use the following syntax - `${variable_name}` to properly wrap these values
 
-Take a look at these two sentences, one using concatenatoion, the other using interpolation.
+Take a look at these two sentences, one using concatenation, the other using interpolation.
 
 ```JavaScript
 var quantity = 12;