diff --git a/_includes/base-capstone-instructions.md b/_includes/base-capstone-instructions.md deleted file mode 100644 index 7edbf96..0000000 --- a/_includes/base-capstone-instructions.md +++ /dev/null @@ -1,9 +0,0 @@ -In order to make you as successful as possible during your time here, we have collected readings and exercises for you to complete prior to beginning Mod 1. This capstone helps provide important context, vocabulary, and baseline of skills to help you hit the ground running on the first day of class. We've found that students who come into the program having invested time in familiarizing themselves with key concepts are able to maximize their time at Turing. - -## Capstone Overview - -The Mod 0 Capstone is divided into two sections: Professional Development and Technical. You are required to spend at least 8 days completing these assignments, however it is recommended that you start as soon as possible. If you have more than a week to dedicate to the capstone, make sure you continue to code every day after you have completed the assignments. You SHOULD NOT complete the capstone early and take an extended break from coding before your first day of class. This is very important to make sure you are in a routine that will keep your skills sharp and prepare you to hit the ground running on day 1. - -## Capstone Assignments - -The following assignments are due **according to the date on [turing.io/prep](https://www.turing.io/prep)**. You will submit links to your work there using a google form. diff --git a/_includes/base-prework-instructions.md b/_includes/base-prework-instructions.md new file mode 100644 index 0000000..eb3e28b --- /dev/null +++ b/_includes/base-prework-instructions.md @@ -0,0 +1,9 @@ +In order to make you as successful as possible during your time here, we have collected readings and exercises for you to complete prior to beginning Mod 1. This pre-work helps provide important context, vocabulary, and baseline of skills to help you hit the ground running on the first day of class. We've found that students who come into the program having invested time in familiarizing themselves with key concepts are able to maximize their time at Turing. + +## Mod 1 Pre-work Overview + +The Mod 1 Pre-work is divided into two sections: Professional Development and Technical. You are required to spend at least 8 days completing these assignments, however it is recommended that you start as soon as possible. If you have more than a week to dedicate to the mod 1 pre-work, make sure you continue to code every day after you have completed the assignments. You SHOULD NOT complete the mod 1 pre-work early and take an extended break from coding before your first day of class. This is very important to make sure you are in a routine that will keep your skills sharp and prepare you to hit the ground running on day 1. + +## Pre-work Assignments + +The following assignments are due based on your mod 0 section and can be found on the [mod 0 calendar](mod0.turing.io#calendar) diff --git a/_includes/navigation.html b/_includes/navigation.html index c9dd964..2e13a4c 100644 --- a/_includes/navigation.html +++ b/_includes/navigation.html @@ -9,14 +9,12 @@ diff --git a/_includes/pd-gu-capstone-instructions.md b/_includes/pd-gu-prework-instructions.md similarity index 65% rename from _includes/pd-gu-capstone-instructions.md rename to _includes/pd-gu-prework-instructions.md index a11e34e..2c00b14 100644 --- a/_includes/pd-gu-capstone-instructions.md +++ b/_includes/pd-gu-prework-instructions.md @@ -14,19 +14,10 @@ The assignments below will be submitted in gists that you will create on your Gi * click Create Public Gist * You can also visit [gist.github.com](https://gist.github.com/) -We take these exercises seriously, and we ask that you do too. We expect at minimum 4-6 sentences in response to **each** question, but feel free to expand and elaborate as you deem necessary. Use Markdown to organize your gists clearly with the question above the response like so: -
-

What is the value of a checklist?

-

Your response here.

-
-

What do you plan to improve upon while at Turing?

-

Your response here.

-
- Don't worry about the color or the boxes within the formatting, but the above has the heading and response format that will help us read through these clearly and efficiently, while giving you some practice with ```.md``` files. - - Use these exercises to start telling your unique story with your distinct experiences. This is something we will continue to practice during your time at Turing. +We take these exercises seriously, and we ask that you do too. We expect at minimum 4-6 sentences in response to **each** question, but feel free to expand and elaborate as you deem necessary. Use Markdown (this is a programming language used for writing) to format your gists. + +Use these exercises to start telling your unique story with your distinct experiences. This is something we will continue to practice during your time at Turing. #### [Professional Development Assignment](https://github.com/turingschool/career-development-curriculum-site/blob/master/module-0-capstone/career_development_capstone.md) #### [Gear Up Assignment](https://github.com/turingschool/gear-up/blob/master/pre-work/intro_with_empathy.markdown) - diff --git a/calendar/index.md b/calendar/index.md new file mode 100644 index 0000000..482abf4 --- /dev/null +++ b/calendar/index.md @@ -0,0 +1,6 @@ +--- +layout: page +title: Mod 0 Calendar +--- + + diff --git a/homework/index.md b/homework/index.md new file mode 100644 index 0000000..ef00e74 --- /dev/null +++ b/homework/index.md @@ -0,0 +1,12 @@ +--- +layout: page +title: Homework +--- + +All of the homework for mod 0 can be found on the [mod 0 project board](https://github.com/turingschool/mod-0/projects/1) + +This project board uses a methodology called kanban (I would google the term if you're unfamiliar) + +You'll be using an app called [conveyor belt](http://conveyorbelt.herokuapp.com/) to create your own copy of the board above. This will allow you to track your progress on the homework over time by moving each card to the done column when you've completed it. + +When you've finished your homework, and you're looking for something to do, you can always rely on the mod 1 pre-work as that outlet! Just find the link in the sidebar for your program. diff --git a/index.md b/index.md index d490e0f..2074734 100644 --- a/index.md +++ b/index.md @@ -7,7 +7,7 @@ Hi there and welcome! ## What is Mod 0? -Mod 0 is a prerequisite course for both of the programs at Turing. It is a structured series of 5 classes which take place remotely during the evening, and ideally starts 6 weeks before you begin your full-time FEE or BEE course at Turing. These classes are not in person, and are conducted fully remotely via Zoom. Please check the [calendar](https://sites.google.com/casimircreative.com/enrollment/documents-and-info/events-mod-0-calendar) for session dates. +Mod 0 is a prerequisite course for both of the programs at Turing. It is a structured series of 5 sessions which take place remotely during the evening, and ideally starts 6 weeks before you begin your full-time FEE or BEE course at Turing. These classes are not in person, and are conducted fully remotely via Zoom. Please check the [calendar]({{ site.baseurl }}/calendar) for session dates. The goals of mod 0 are to: * Understand the systems and behaviors needed to be successful at Turing and as a software developer @@ -31,7 +31,3 @@ The key tools and concepts we go over in mod 0 are: ## Next steps When you're ready to get started, click over to [environment setup instructions]({{ site.baseurl }}{% link setup-instructions.md %}) and start installing! - -## Calendar - - diff --git a/capstone/be_engineering/index.md b/prework/be_engineering/index.md similarity index 52% rename from capstone/be_engineering/index.md rename to prework/be_engineering/index.md index fe699a9..e477548 100644 --- a/capstone/be_engineering/index.md +++ b/prework/be_engineering/index.md @@ -1,33 +1,32 @@ --- layout: page -title: Module 0 Capstone +title: Module 1 Pre-work subheading: Back End Engineering --- -{% include base-capstone-instructions.md %} +{% include base-prework-instructions.md %} -{% include pd-gu-capstone-instructions.md %} +{% include pd-gu-prework-instructions.md %} -### Technical Capstone +### Technical Pre-work -The technical capstone can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day. +The technical mod 1 pre-work can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day. -At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This capstone is designed to get you into that essential routine before day one of class. +At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This pre-work is designed to get you into that essential routine before day one of class. -After completing the capstone, you should be able to do the following: +After completing the pre-work, you should be able to do the following: * Be comfortable navigating your development environment and using your tools (Atom, Chrome, the console, and the command line) * Develop a basic knowledge of Ruby in order to build a simple program (for show and tell) -If you have more than 7 days to work on the capstone, you should break up the work and complete the Next Steps section below so that you are coding every day! +If you have more than 7 days to work on the pre-work, you should break up the work and complete the Next Steps section below so that you are coding every day! The link below will take you to the Github page that contains all the Technical work. Scroll through the page to find the instructions for getting your computer setup and getting started. -#### [Click here to get started with the Technical Capstone](https://github.com/turingschool-examples/backend_module_0_capstone) +#### [Click here to get started with the Technical Mod 1 Pre-work](https://github.com/turingschool-examples/backend_mod_1_prework) ### Next Steps -Before moving any further, complete all of the projects listed in Day 7 of the Module 0 Capstone Repository. +Before moving any further, complete all of the projects listed in Day 7 of the Module 1 Back-End Pre-work Repository. If you have more time, review the [Back End Curriculum Site](http://backend.turing.io/) for additional resources. - diff --git a/capstone/fe_engineering/expandCollapse.js b/prework/fe_engineering/expandCollapse.js similarity index 100% rename from capstone/fe_engineering/expandCollapse.js rename to prework/fe_engineering/expandCollapse.js diff --git a/capstone/fe_engineering/index.md b/prework/fe_engineering/index.md similarity index 58% rename from capstone/fe_engineering/index.md rename to prework/fe_engineering/index.md index 860fe7c..bb46f67 100644 --- a/capstone/fe_engineering/index.md +++ b/prework/fe_engineering/index.md @@ -1,40 +1,41 @@ --- layout: page -title: Module 0 Capstone +title: Module 1 Pre-work subheading: Front End Engineering --- -{% include base-capstone-instructions.md %} +{% include base-prework-instructions.md %} -{% include pd-gu-capstone-instructions.md %} +{% include pd-gu-prework-instructions.md %} -### Technical Capstone +### Technical Pre-work -The technical capstone can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day. +The technical pre-work can be completed in 8 days, with one day for setup. However, it is highly recommended that you begin immediately. It is expected that you spend a few hours of concentrated effort on the tasks for each day - about 30 hours total. This should help you to establish a routine of coding every day. -At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This capstone is designed to get you into that essential routine before day one of class. +At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you've learned. This pre-work is designed to get you into that essential routine before day one of class. -After completing the capstone, you should be able to do the following: +After completing the pre-work, you should be able to do the following: * Be comfortable navigating your development environment and using your tools (Atom, Chrome, the console, and the command line) * Develop a basic knowledge of HTML, CSS, and JavaScript code in order to build a simple, static web page (for show and tell in week 1!) -If you have more than 7 days to work on the capstone, you should break up the work and complete the Next Steps section below so that you are coding every day! +If you have more than 7 days to work on the pre-work, you should break up the work and complete the Next Steps section below so that you are coding every day! #### What You'll Need -Items you need to complete the mod 0 capstone: +Items you need to complete the mod 1 pre-work: * The books: [Web Design with HTML, CSS, JavaScript and jQuery Set](https://www.amazon.com/Web-Design-HTML-JavaScript-jQuery/dp/1118907442/ref=sr_1_2?ie=UTF8&qid=1541193719&sr=8-2&keywords=duckett) -* A consistent internet connection + * These can be found online for free. After some quick googling it looks like they can be found here + * [html & css](https://www.pdfdrive.com/html-css-e16578853.html) + * [javscript & jquery](https://www.pdfdrive.com/javascript-and-jquery-interactive-front-end-web-development-e195248768.html) The link below will take you to the Github page that contains all the Technical work. Scroll through the page to find the instructions for getting your computer setup and getting started. -#### [Click here to get started with the Technical Capstone](https://github.com/turingschool-examples/frontend-module-0-capstone) +#### [Click here to get started with the Technical Mod 1 Pre-work](https://github.com/turingschool-examples/frontend-mod-1-prework) ### Next Steps -Before moving any further, complete all of the exercises listed [here](https://github.com/turingschool-examples/frontend-module-0-capstone#month-of-module-0-capstone-extended-resources). +Before moving any further, complete all of the projects listed in Day 7 of the Module 1 Front-End Pre-work Repository. If you have more time, review the [Front End Curriculum Site](http://frontend.turing.io/) for additional resources. - diff --git a/capstone/fe_engineering/tools.html b/prework/fe_engineering/tools.html similarity index 100% rename from capstone/fe_engineering/tools.html rename to prework/fe_engineering/tools.html diff --git a/session1/index.md b/session1/index.md index 2f09189..24b2fb7 100644 --- a/session1/index.md +++ b/session1/index.md @@ -105,7 +105,7 @@ Turing is a very challenging experience for most people. To be successful here, ### Communication -Make sure that you've added the **[Mod 0 Calendar](https://calendar.google.com/calendar?cid=Y2FzaW1pcmNyZWF0aXZlLmNvbV8xMnA0NjkzaG1lcjFvcmNlcHA3NHZnNzdwZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)** to your own calendar. This is where you will find all mod 0 related events, including sessions, capstone study sessions, and other community wide events. +Make sure that you've added the **[Mod 0 Calendar](https://calendar.google.com/calendar?cid=Y2FzaW1pcmNyZWF0aXZlLmNvbV8xMnA0NjkzaG1lcjFvcmNlcHA3NHZnNzdwZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)** to your own calendar. This is where you will find all mod 0 related events, including sessions, mod 1 pre-work study sessions, and other community wide events. We will also remind you when these events are via **[slack](https://turingschool.slack.com/)**, which is the **primary mode of communication** we use at Turing. Make sure that you're checking it once a day so that you can stay up to date. It's also a great place to ask questions if you are running into issues, as people are likely experiencing the same issue that you are. @@ -664,5 +664,3 @@ In addition, consider the following questions: ## Homework Find the homework in your Mod 0 Project Board. Contact David, Ellen, or Mason if you're stuck (or better yet, post in the public slack channel as you're likely not the only one running in to that issue) - -Capstones (program specific pre-work) are another good thing to get a head start on. They can be found on the mod 0 website in the sidebar and are due 6/10. Plan on ~40 hours in total. diff --git a/session2/index.md b/session2/index.md index feac5f3..0fb7106 100644 --- a/session2/index.md +++ b/session2/index.md @@ -54,7 +54,7 @@ subheading: Terminal, File/folder Structure, Git Basics - We'll stay on the call at the end of today's session for any Qs that are not addressed during the lesson. - You'll receive feedback on homework from either Alice, Margo, Mason, or David. Check your homework gists!!! -- Where are you on your capstone? They're due June 10th! +- Where are you on your pre-work? It's due June 10th! ### Today's Goals diff --git a/session3/index.md b/session3/index.md index 6220276..1a4160f 100644 --- a/session3/index.md +++ b/session3/index.md @@ -409,5 +409,3 @@ git push origin master ## Homework and GitHub Projects Business as usual. Reach out on slack if you're stuck! - -Capstone is due next Wednesday! Aim to be finished with day 5 by the weekend! diff --git a/session4/index.md b/session4/index.md index 3127dd4..69380b1 100644 --- a/session4/index.md +++ b/session4/index.md @@ -46,7 +46,6 @@ subheading: Scavenger Hunt, Modeling OOP, Assessment Expectations - Leaving feedback directly on homework gists. Make sure you're checking them. We'll have session 2 + 3 feedback to y'all be end of the weekend. - Remember to be aware of where you are in your directory structure of the terminal before you clone anything down or start running git commands. Always run ls after cloning -- We don't expect you to be masters at all the things in your capstone. It's really your mod 1 prework - We understand that things are crazy right now. Be kind and gentle with yourselves and others. If you need anything from us, don't hesitate to reach out. Remember that proactive communication is always best. ### Other Notes @@ -328,7 +327,7 @@ This is our final Mod 0 technical session. Your assignment between now and Sessi
  1. Open up your ... file in your text editor.
  2. -
  3. You'll be given directions for some exercises that are program specific. Looking for something to study? Check out session 1 on data types and variable assignment. The capstone is also a good resource.
  4. +
  5. You'll be given directions for some exercises that are program specific. Looking for something to study? Check out session 1 on data types and variable assignment. The mod 1 pre-work is also a good resource.
  6. If you are really solid with data types and variable assignment, it shouldn't be too bad
  7. Save your file.
  8. Add and commit your changes.
  9. diff --git a/session5/index.md b/session5/index.md index 71427a3..36bc37c 100644 --- a/session5/index.md +++ b/session5/index.md @@ -43,8 +43,8 @@ subheading: Attention to Detail and Iteration ### Follow-Ups -- Capstones are due this Wednesday! Get on it! -- We will have assessment and capstone feedback to everyone by EOD Monday +- Prework is due this Wednesday! Get on it! +- We will have assessment and prework feedback to everyone by EOD Monday ### Today's Goals @@ -334,8 +334,8 @@ We'll go into breakout rooms to briefly discuss the syntax for iterating in Ruby * Keep up the hard work * Keep asking questions in your cohort channels * Ellen, Mason and David are still around if you need us - * Capstone is due Wednesday (see your mod 0 calendar) + * Prework is due Wednesday (see your mod 0 calendar) * Learning to code is much more like exercise than epiphanies - Think about MJ! -> Quote from Meg Stang (BE instructor) - "I've noticed that the students that do the bare minimum on their mod 0 capstone are the ones that usually struggle for at least the first half of the mod." +> Quote from Meg Stang (BE instructor) - "I've noticed that the students that do the bare minimum on their mod 1 pre-work are the ones that usually struggle for at least the first half of the mod." diff --git a/session5/index.md.b b/session5/index.md.b deleted file mode 100644 index c08010c..0000000 --- a/session5/index.md.b +++ /dev/null @@ -1,367 +0,0 @@ ---- -layout: page -title: Session 5 -subheading: Attention to Detail and Iteration ---- - -
    -
    -

    Goals

    - By the end of this session, you will be able to: -
      -
    • apply strategies to identify issues in syntax and style
    • -
    • define iteration in programming
    • -
    • demonstrate iteration in real-world and programming situations
    • -
    -
    -
    -

    Agenda

    - -
    -
    -

    Materials

    -
      -
    • Notebook
    • -
    • Writing instrument
    • -
    • Laptop
    • -
    • Headphones & mic
    • -
    -
    -
    - -## Housekeeping and Goals - -### Wins - -- You finished the assessment! - -### Follow-Ups - -- We'll have scores back to y'all by the end of the weekend. -- Be sure to use the formula pinned in the channel when asking technical questions -- Capstone is due in a couple weeks! Get on it! - -### Today's Goals - -(See above) - -## Intros, Review, and Icebreaker - -
    -

    Intros, Review, and Icebreaker

    -

    Person with the shortest first name goes first.

    -

    1. Introduce yourself: name, pronouns

    -

    2. What is a book, tv show, or movie that you've read/watched recently and really enjoyed? Why?

    -

    3. Accountability review: what tangible progress have you made toward your mod 0 focus skills?

    -

    4. Determine who will bring your breakout group questions back to the whole group

    -

    Have extra time? Share what extra things you're doing to get ready to start school at Turing.

    -
    - - -## Attention to Detail - -After reflecting on and trying to find patterns for the people who are struggling in mod 1, we've identified that attention to detail is one of the main themes we've seen. - -Attention to detail is something that constantly comes up when coding -* A missing or misplaced character can make your code behave in an entirely different way -* Documentation is super dense, you'll likely need to read it at least couple of times before you're able to understand and apply it -* Tutorials and directions for implementation are common place. If you miss one step, you won't get the same result - -### Identifying Mistakes - -#### Breakout Groups (10 minutes) -Go through the following examples, and determine whether or not each piece of code is syntactically correct. Even if the line of code is syntactically correct, are there any other mistakes in it? - -Be sure to pay attention to how your capstone is formatted. If people have poorly formatted gists and repos for their capstone, it is a bit of a red flag on our end for this reason. - -As a group, either in your text editors, or in a notebook, write down your answers for each number below. Be sure to deliberate as a group and try your best to explain **why** you expect something to work or not. - -``` -1. bestFoodOfAllTime = 'burritos' - -2. isIt = true - -3. secondBestFood = 'ramen' - -4. sandwich = "taco?' - -5. phoneNumber = '123-456-7890' - -6. bestFoodOfAllTime - -7. isLying = False - -8. animals = ['donkey', 'giraffe', 'elephant', 'chimpanzee'] - -9. secondBestfood - -10. sandwiches = ['cheesesteak', 'po' boy', 'reuben'] - -11. drinkSize = 12 oz - -12. ,2 * 2 - -13. 4 / 2 - -14. (6 * 2) + (6 / 3) / 6) - -15. grads = { "9th grade": 110, "10th grade": 125, "11th grad": 66 } - -16. -instructors = { - "Mod 0": "Tim and David", - "Mod 1": 'Mike and Sal", - "Mod 2": "Brittany and Robbie" -} -``` - -What were your strategies when trying to figure out if a piece of code is syntactically correct or not? - -Did you do any experimentation? Did you reference any documentation? - -Key things to think about when looking for syntax errors: -* parentheses, quotes, brackets, and braces are all like shoes, useless without their mate -* consistency is key. If you're looking through code that has inconsistent indentation, casing, quote types some mental overhead is being used where it doesn't need to be - -### Syntax and Style - -Syntax and Style are both essential when it comes to writing code. - -Syntax refers to the structure of statements in a computer language. Are quotes surrounding both sides of a string? No, then the language will throw an error. If your code isn't working because of a placement of a character, it's a syntax issue. - -Style doesn't determine if a piece of code runs or not. Its purpose is to make code more readable. Ideally, when you're working on a team, you and your teammates are following similar patterns (conventions) when it comes to things like whitespace (including indentation) or double vs single quotes. What is one of those conventions you've already been using? - -Let's take a look at what these two things might look like in action: - -Difference in syntax - -``` -one doesn't work - -animals = ['donkey', 'giraffe', 'elephant', 'chimpanzee'] - -animals = ['donkey', 'giraffe', 'elephant' 'chimpanzee'] -``` - -Difference in style - -``` -both work below, but which reads better? - -animals = ['donkey', 'giraffe', 'elephant', 'chimpanzee'] - -animals=["donkey",'giraffe','elephant',"chimpanzee"] -``` - -If you want to find code that is both syntactically correct and using good style the best place to look is going to be the docs (mdn for JavaScript and ruby-doc for Ruby). The code examples are a great place to look to see if you are writing your code in a similar way. Also, keep in mind that things like casing of variables is another good way to stay consistent and maintain good style. - -## BREAK - -Turn off your mics and videos and walk away from the computer. Stand up, stretch, drink water. Do a few sit-ups, squats, push-ups, jumping jacks, arm circles, stress ball squeezes, or whatever else moves your body. -
    - - -## Iteration - -Iteration (or looping for a specified number of times) is a process of repeating a task for each object in a collection. For each of the scenarios below, we'll walk through using props to demonstrate the concept. - -### Iteration in Real Life - -These are examples that would be programatically challenging because they would require a ton of steps, but are things that we do everyday. - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ScenarioCollectionFor each...Do this:Then:
    Grading paperspaperspaper -
      -
    1. read through it
    2. -
    3. mark the score on the top
    4. -
    -
    repeat with next paper
    Feeding animalsanimalsanimal -
      -
    1. bring the animal to the food bucket
    2. -
    3. allow the animal to eat
    4. -
    5. bring animal back to barn
    6. -
    -
    repeat with next animal
    - -### Iteration in Programming - -By "in programming", we mean things that could be done, with relative ease, by a computer. Like crunching numbers. - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ScenarioCollectionFor each...Do this:Then:
    Calculating max heart ratebirth yearsyear -
      -
    1. subtract birth year from 2019 to get age
    2. -
    3. subtract age from 220
    4. -
    -
    repeat with next year
    Formatting namesnamesname -
      -
    1. capitalize the first letter
    2. -
    3. lowercase all remaining letters
    4. -
    -
    repeat with next name
    - -
    -

    Try It: Iteration in Real Life and Programming

    -

    Brainstorm a real life scenario that uses iteration. Fill out the table below and be ready to share.

    - - - - - - - - - - - - - - - - - - - -
    ScenarioCollectionFor each...Do this:Then:
    -

    Think back to your grocery store app. What is something you said you'd keep inside of an array? Why might you need to iterate over that collection? Jot down your scenario below.

    - - - - - - - - - - - - - - - - - - - -
    ScenarioCollectionFor each...Do this:Then:
    -
    - -### Iteration Syntax - -We'll go into breakout rooms to briefly discuss the syntax for iterating in Ruby and JavaScript. - -
    - Are you a or student? - - -
    - - -### Other Reminders - -* This is your last technical session, next session will be with Emma, where she'll talk more about life in person at Turing -* When you start working on Mythical Creatures in Mod 1, think back to OOP, classes and methods in mod 0 -* Moving forward: - * Keep up the hard work - * Keep asking questions in your cohort channels - * Ellen, Mason and I are still around if you need us - * Capstone is due in a couple weeks! (see your mod 0 calendar) - -* Learning to code is much more like exercise than epiphanies - -> Quote from Meg Stang (BE instructor) - "I've noticed that the students that do the bare minimum on their mod 0 capstone are the ones that usually struggle for at least the first half of the mod." diff --git a/sessions/index.md b/sessions/index.md new file mode 100644 index 0000000..853ee53 --- /dev/null +++ b/sessions/index.md @@ -0,0 +1,10 @@ +--- +layout: page +title: Mod 0 Sessions +--- + +* [Session 1]({{ site.url }}/session1) - covers orientation, googling, and data types +* [Session 2]({{ site.url }}/session2) - covers terminal and git +* [Session 3]({{ site.url }}/session3) - git and github +* [Session 4]({{ site.url }}/session4) - covers object oriented programming +* [Session 5]({{ site.url }}/session5) - covers iteration and other useful skills you'll need in mod 1