Merge branch 'main' of github.com:turingschool/curriculum-site

module0/index.md

@@ -16,7 +16,7 @@ title: Welcome to Module 0
   </tr>
   <tr>
     <td>2412 (Dec 2)</td>
-    <td>November 4 - November 10</td>
+    <td>November 11 - November 15</td>
   </tr>
 </table>
 

module4/lessons/art_of_the_graceful_exit.md

@@ -0,0 +1,102 @@
+---
+layout: page
+title: Art of the Graceful Exit
+---
+
+## Learning Goals
+
+- Develop a strategy to responding to interview questions when you don't know the answer.
+- Identify the personal qualities you want to convey when answering interview questions.
+
+<section class="call-to-action">
+### Warm Up
+
+Think about or imagine an interview where you were asked a question you did not know the answer to. How did you feel? How did you answer? What impressions do you think the interviewer had of you based on how you answered? 
+
+</section>
+
+## Purpose of an Interview
+
+What is the job of the interviewer?
+
+Of course they are asking you some knowledge-based questions to see what you know and what you don't know, but more importantly, they are trying to figure out what it would be like working with you.
+
+What type of person are you? What are you like working with teams? How much direction, supervision, and assistance will you need? 
+
+When answering interview questions, you are providing the interviewer with lots of insight and information about the personal qualities you will bring to their team.
+
+<section class="call-to-action">
+
+Take a minute and jot down the personal qualities you would like the interviewer to walk away knowing about you.
+
+Examples:
+- curious
+- enthusiastic
+- humble
+- hard-working
+- growth mindset
+- good problem-solver
+
+Keep these qualities in mind as you start to formulate your answers to questions you don't know the answer to. Even if we can't give them the correct technical answer, we can still leave them with more knowledge about who we are as a developer, a teammate, and a human.
+
+</section>
+
+## Some Example Responses 
+Here are some ideas to help you respond to an interview question when you aren't exactly sure of the answer.
+
+<section class="dropdown">
+### Clarifying Questions
+
+Interview question: "Can you give me some examples of how you might optimize an application?"
+Response: "By optimizing an application, do you mean making it faster? Could memoization or caching be an example of this?"
+
+What qualities is the interviewee displaying when they ask questions like this? 
+</section>
+
+<section class="dropdown">
+### Pivot
+
+Response: "I'm not familiar with that concept, but it reminds me of ________ . Could I talk a bit about that instead?"
+
+What qualities is this interviewee displaying?
+</section>
+
+### Instructors Demonstrate Graceful (and Graceless) Interview Answers
+
+As the instructors demonstrate an interview response that is clearly not ideal, reflect on these questions:
+1. What does this answer tell you about the interviewee? What qualities does it convey?
+1. What might it be like working with this person? 
+1. What could the interviewee do to improve their answer?
+1. What skills _could_ you demonstrate through your answer?
+
+Now as the instructors demonstrate a more acceptable response, consider the same questions above.
+
+
+### Breakout Rooms
+
+Take turns being the interviewer and the interviewee. 
+
+As the interviewee, even if you do know the answer, pretend you do not so you can practice a graceful exit.
+
+After the interviewee answers, the rest of the group can give kind and actionable feedback, again referring to the questions above about what additional information the answer tells you about the candidate.
+
+<section class="call-to-action">
+
+  1. Can you tell me about the benefits of MVC Architecture?
+  2. How would you explain MVC architecture in terms of a React application? 
+  3. What are the benefits of a relational database and what are some alternatives?
+  4. What is an interface?
+  1. What are some ways you can show that your web application is accessible? 
+  2. How does JavaScript handle multiple requests given that it’s a single-threaded language? 
+  3. What are the advantages of REST over other http protocols? 
+  4. What is an interface?
+
+</section>
+
+
+### Reflection
+
+In a notebook, write down your reflections to these questions:
+1. What are your biggest takeaways from this lesson?
+1. What qualities about yourself are you wanting to convey in an interview and how can you accomplish this?
+1. How will you gracefully exit an interview question where you do not know the answer? 

module4/lessons/index.md

@@ -4,6 +4,7 @@ title: Module 4 - Lessons
 ---
 
 ### Lessons
+- [Art of the Graceful Exit](./art_of_the_graceful_exit)
 
 ### Additional Lesson Resources
 - [Rebase Workflow](./rebase_workflow)

module4/projects/personal_portfolio/index.md

@@ -3,14 +3,97 @@ title: Personal Portfolio
 layout: page
 ---
 
-## Learning Goals
-
 
 ## Overview
+Your personal portfolio is a place to highlight your work and skills. It can be used during your job hunt - you can send out links to your profile, and Turing staff may share your profile to employers who come to us asking for candidates.
+
+## Setup and Submission
+You can either use this provided [template](https://github.com/turingschool/portfolio-template) or create your own portfolio from scratch. You should include all content listed below regardless of which route you choose.
+
+When you are finished, submit the URL to your portfolio using this [submission form](https://forms.gle/3WiWnpZEKu2oUAaJ7).
+
+<section class="note">
+  This is due by EOD Friday of week 4. You are welcome and encouraged to submit earlier for feedback.
+</section>
+
+## Required Content
+
+1. Title (ex: Software Developer)
+2. Professional-looking photo
+  * This should be a photo of just you (no kids or animals, sorry!)
+  * Use the same photo as your LinkedIn and GitHub profiles if possible
+3. About Me Description
+  * Tell your professional story
+  * Consider how this is consistent with your LinkedIn and overall brand
+  * See below for more details on this section
+  * Make sure to have someone else review this section for clarity, spelling, and grammar
+4. Email address
+5. GitHub profile link
+6. LinkedIn profile link
+7. Polished copy of resume
+8. Preferred Locations
+9. Previous Industries
+  * Limit to 5 previous industries. If you are concerned about this, please reach out to your Career Specialists.
+10. Skills
+11. At least 2 projects
+  * Show variety: paired, team, individual
+  * Include screenshots for any project with a frontend
+  * Tools Used
+  * Code repository link and Deployed link if available
+  * See below for more details on project descriptions
+<section class="dropdown">
+### About Me
+What do you want your profile to say about you? Write out a rough draft of your professional story considering using this framework:
+  * What is your career story about your past, present, and future that you want to share with employers?
+  * What prior experiences are relevant and transferable to the tech industry?
+  * What impact you want to have in software development?
+  * What kind of company and culture are you passionate about adding value for?
+
+In this section, make sure to answer the following questions:
+  * Who am I?
+  * Why am I in this field?
+  * What’s next for me?
+
+Show readers who you are by telling a story of your journey into tech. Share enough for them to want to hear and learn more!
+
+**Your Portfolio _About Me_ section, LinkedIn summary, and resume summary (if you chose to use one) should all be slightly different.**
+  * You want the reader to learn something new with each profile
+  * Each summary has a different purpose; think about the audience
+  * Resume summaries should tell why you are the best candidate for the role relevant to the job description.
+  * LinkedIn summaries allows you to add a personal touch in addition to relevant skills and experiences that will attract recruiters and hiring managers.
+  * The Portfolio is similiar to the LinkedIn audience; employers want to know your backstory, your value proposition and what’s next for you as a developer.
+</section>
+<section class="dropdown">
+### Projects
+The main recommendation here is to remember that you are speaking to potential employers, not investors. These project descriptions should briefly describe the project, and then quickly pivot to describing your primary contributions and the things you learned. **This is an advertisement for you, not the project.**
+
+Be consistent in your project descriptions. Too often students use different formats and headings for each of their project descriptions. It can help your audience of potential employers to quickly digest this information if the order in which you provide information is consistent across projects.
 
+A good format to follow is:
+  * First sentence: name of project, number of collaborators, primary technologies used, what it does.
+  * Second sentence: main learning goals of the project & the things you were doing for the first time in this project (if you don’t know, ask your instructors).
+  * Third sentence: any stretch goals you were able to achieve.
+  * Fourth sentence: anything you specifically focused on in the project.
 
-## Expectations
+  <section class="call-to-action">
+  Examples:
 
+  * Terminal Crawler provides users a CLI that scrapes Turing’s Terminal site to check alumni profiles for broken project links. This is the first project that I’ve tackled outside of the Turing curriculum, which has given me an opportunity to explore topics not covered in class. At this point I’ve created a simple CLI that scrapes the Terminal site and successfully identifies broken links. I’m currently planning on adding the option to send email notifications from this plain old Ruby project to users who have broken links in their profiles, and potentially implementing background workers to give users the ability to get back to work rather than waiting for those emails to send.
+  * My Name is Dad is an app that randomly generates dad jokes to new dads in training that I created with a team of two other developers. During this 10 day stretch project we prioritized self-teaching and implementing the state management library, Redux, for a small scale app. My primary responsibilities on this project included managing all CSS styling and animations, directing the team with decision making, and monitoring quality control. I also helped my team members test our project using Cypress and use Redux to update and manage the state of our application.
+  </section>
+</section>
+<section class="dropdown">
+### Nice to Haves
+Nice to have but not required:
+* Pronouns
+* Skills you are currently learning
+* Twitter/X profile
+* Project collaborators
+* Deployed Project links
+</section>
 
 ## Evaluation Details
+Your portfolio is due by EOD Friday of week 4 via the submission form above.
+**A passing portfolio will include all 11 of the required pieces of information listed above.** If any are missing or incomplete, the project will not be considered passing until those sections are completed.
 
+Completion of your portfolio is a graduation requirement.