You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li>I typically work from <strong>9 AM to 5 PM</strong>, but I’m generally available until <strong>7 PM</strong> if something urgent comes up.<br/></li>
16
+
<li>I’m a <strong>morning person</strong>—I like to knock out my most important tasks early in the day.<br/></li>
17
+
<li>I prefer <strong>in-person meetings</strong> over chat when possible.</li>
18
+
<li>Feel free to <strong>interrupt me</strong>, just give me a <strong>heads-up first</strong>.</li>
19
+
<li>If I can't assist you right away, please try another team member first. If no one’s available, feel free to <strong>reach out to me on my personal number</strong>.</li>
20
+
</ul>
21
+
22
+
<h2>💬 Communication Style</h2>
23
+
<hr/>
24
+
<ul>
25
+
<li>I prefer to give and receive <strong>feedback via email</strong>—it helps me process and respond more thoughtfully.<br/></li>
26
+
<li>I'm generally responsive during work hours, but I appreciate some heads-up for anything time-sensitive.</li>
27
+
<li>For non-urgent matters, email is the best way to ensure I don’t miss anything.</li>
28
+
</ul>
29
+
30
+
<h2>📌 Priorities</h2>
31
+
<hr/>
32
+
<ul>
33
+
<li>I focus on <strong>clarity, consistency, and quality</strong> in customer service.</li>
34
+
<li>I value <strong>transparency and ownership</strong>—I’m happy to collaborate, but I appreciate when people take initiative.</li>
35
+
</ul>
36
+
37
+
<h2>🧘♀️ Personal Preferences</h2>
38
+
<hr/>
39
+
<ul>
40
+
<li>I get <strong>migraines</strong> occasionally, and they hit hard. If I seem off, that might be why.</li>
41
+
<li>I work best with a bit of quiet time to focus. I don’t mind background noise, but I like having blocks of time without distractions.</li>
42
+
<li>A quick <strong>coffee and a playlist</strong> go a long way for my productivity.</li>
43
+
<li>I appreciate people who are <strong>direct but kind</strong>.</li>
44
+
</ul>
45
+
46
+
<h2>🆘 When Things Go Wrong</h2>
47
+
<hr/>
48
+
<ul>
49
+
<li>If something urgent happens and I’m unavailable, don’t hesitate to escalate or involve someone else.</li>
50
+
<li>If there's ever a miscommunication, I'm open to a quick, honest conversation—no drama needed.</li>
51
+
</ul>
52
+
53
+
<h2>💡 Fun Facts</h2>
54
+
<hr/>
55
+
<ul>
56
+
<li>I love <strong>Lo-fi music</strong>—it helps me focus and unwind.</li>
57
+
<li>I’m always down for a good <strong>YouTube Music playlist recommendation</strong>.</li>
58
+
<li>I enjoy reading, organizing things, and drinking Starbucks Refreshers no matter the season.</li>
59
+
<li>Favorite quote: <em>“Everything is gonna be okay in the end, and if it's not okay, then it's not the end.”</em></li>
* Make sure to sync your fork before creating a branch in order to pull in the latest changes.
19
+
* Sync your branch often to avoid merge conflicts and execute `git pull` to bring the latest changes to your machine.
20
+
* If your branch is too far behind or you run into too many issues, feel free to delete and re-create your repository. Make sure to review the article linked at the bottom of the [lesson_00](/lesson_00/README.md) README for instructions on how to create your fork and branch properly.
21
+
* Remember, you should not reuse a branch you've used to submit a pull request. If you need to make changes, create a new branch and work from there after you've updated your fork to the latest.
22
+
23
+
### Creating new quiz questions
24
+
25
+
Now's your chance to quiz the instructor! In this assignment, you will modify the quiz project to include three quiz questions based on the content you've learned in this course so far. Feel free to choose any topic for your questions.
26
+
27
+
1. Navigate to the [quiz][quiz-folder] directory and install the required dependencies.
2. You will create a quiz file in the [quizzes folder][quizzes-folder]. You should model yours after the example provided in [anthony_mays_quiz.ts][quiz-example]. Note that the name of the file you create should match the name of the class in the file.
35
+
3. Make sure to provide a unique provider name for your questions provider. You'll need this name to provide answers in step 5.
36
+
```typescript
37
+
getProviderName(): string {
38
+
return'<your unique name goes here>';
39
+
}
40
+
```
41
+
4. Make at least three questions for your quiz and _leave them unanswered_.
42
+
5. To provide answers, you will need to update the [quiz.yaml][test-config-file] file in the test directory. You can copy the example in the file to get started, but you must provide your own answers. To generate an encrypted answer, use [bcrypt.online](https://bcrypt.online).
43
+
6. Lastly, you'll need to modify the [quizzes.module.ts][quizzes-module] file to include your quiz.
44
+
7. Before attempting to submit your quiz, make sure to run the linter on the code and run the tests to ensure that you've updated things correctly. The commands must be run from the [quiz][quiz-folder] sub-folder just like the previous assignment:
45
+
```bash
46
+
npm run check
47
+
```
48
+
8. Once everything passes, submit a PR.
49
+
50
+
**Note: If you want to check that you've encoded your answers correctly, you can update you quiz with the real answers and then run the tests using the command below.
51
+
```bash
52
+
PROVIDER_NAME=<Your provider name here> npm run test
53
+
```
54
+
55
+
### Dealing with merge conflicts
56
+
57
+
Since everyone needs to modify the same files for this assignment, you will most certainly encounter merge conflicts. To resolve this, here are the steps:
58
+
59
+
1. Sync the main branch of your fork and ensure that it is up-to-date.
60
+
2. Use `git checkout main` and `git pull` to get the latest updates pulled down to your computer.
61
+
3. Checkout your feature branch (e.g. `git checkout feature/lesson_03`).
62
+
4. Run `git rebase main` on your feature branch to pull in the latest changes and deal with merge conflicts.
63
+
5. Use the *Source Control* view in VS Code to identify files with conflicts. Click to open them and use the *Merge Editor* to resolve conflicts.
64
+
6. Stage and commit the changed files.
65
+
7. Repeat steps 5-6 until the rebase is complete.
66
+
67
+
An alternative approach is to open the PR and manually edit the conflicting files to work out any issues. This may be easier for some of you, but it can also be tricky to do if you don't know what you're doing.
68
+
69
+
Check out [this YouTube video](https://www.youtube.com/watch?v=OXtdxHTh2oY) for a quick explaination of what's going on.
0 commit comments