# Code Challenge Curriculum

Anything related to code challenges is in this section!

***

## Modules:

* [Unit 0 - Intro to Code Challenges](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-0)
* [Unit 1](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-1)
* [Unit 2](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-2)
* [Unit 3](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-3)
* [Unit 4](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-4)
* [Unit 5](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-5)
* [Unit 6](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-6)
* [Unit 7](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-7)
* [Unit 8](https://raffycastlee.gitbook.io/marcyannotes/codechallenge-curriculum/unit-8)

***

## Outline

### 1. The Tech Interview

* *usually* three buckets:
  1. Behavioral Interviews
  2. Technical Screening
     * the **only** asynchronous step
  3. Technical Interviews

### 2. Tech Interview ~~Prep~~ Routine

* Mastering a programming language
  * Some companies are rigid (can't just use your preference)
* Honing up on the ff:
  1. Problem Solving
  2. Designing **efficient** solutions
  3. **Communicating** solutions using technical technology

### 3. Code Challenge Curriculum

* **Daily** and **Intentional**
  * on leetcode; codesignal *(also generally referred to as GCF, or General Coding Framework)*
  * 60 min after *Mindful Mornings*!
  * sometimes thematic, **MOSTLY** random
  * *catch-ups* available for missed sessions
  * *not graded* but pay attention to **scores**!
    * 389 Score **AT LEAST** three times throughout the program

### 4. Code Challenge Philosphies

> "You can only cook what's in the fridge!"

* Programming is like *cooking*:
  * fridge <<>> knowledge base *(learned!)*
  * tools/equipment would be the natural predisposition *(so don't feel bad; it's not the largest piece in the pie!)*
* Fluency

> "Go slow now to go far later."
>
> * *probably* Reuben (2019)

### 5. Q\&A Takeaways

* PEDAC stands for:
  1. Problem
  2. Example
  3. Data Structure
  4. Algorthm
  5. Code
