mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2025-12-30 03:03:06 -05:00
feat(curriculum): add animations to block 7.1 of the English Curriculum (#55032)
Co-authored-by: DanielRosa74 <58576743+DanielRosa74@users.noreply.github.com>
This commit is contained in:
miyaliu666
@@ -1,6 +1,5 @@
|
||||
---
|
||||
id: 65ddb2ee481da72f38f076ad
|
||||
videoId: nLDychdBwUg
|
||||
title: "Dialogue 1: Introduction to Code Documentation"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-1-introduction-to-code-documentation
|
||||
@@ -8,8 +7,136 @@ dashedName: dialogue-1-introduction-to-code-documentation
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video above to understand the context of the upcoming lessons.
|
||||
Watch the video to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Hey, Brian, I've been assigned to work on this project, and I'm not sure where to start.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 5.48,
|
||||
"finishTime": 7.94,
|
||||
"dialogue": {
|
||||
"text": "Could you help me understand how we should document the code?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 8.5,
|
||||
"finishTime": 13.96,
|
||||
"dialogue": {
|
||||
"text": "Of course. The first thing you should do is create a clear README file that's in the project's root directory.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 14.5,
|
||||
"finishTime": 19.3,
|
||||
"dialogue": {
|
||||
"text": "This file should contain information about the project, its purpose, and how to set it up.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 19.72,
|
||||
"finishTime": 21.8,
|
||||
"dialogue": {
|
||||
"text": "Got it. What else should I include in my README?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 22.22,
|
||||
"finishTime": 27.38,
|
||||
"dialogue": {
|
||||
"text": "You should list the project dependencies so that anyone who wants to work on it knows what they need.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 27.38,
|
||||
"finishTime": 31.96,
|
||||
"dialogue": {
|
||||
"text": "Then specify how to run the code and any other essential setup instructions.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 33.04,
|
||||
"finishTime": 35.96,
|
||||
"dialogue": {
|
||||
"text": "Also, mention coding conventions we follow in this project.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 36.92,
|
||||
"finishTime": 38.78,
|
||||
"dialogue": {
|
||||
"text": "Thanks, I'll make sure to follow your instructions.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 39.28
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 39.78
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,17 +5,12 @@ challengeType: 22
|
||||
dashedName: task-1
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Hey Brian, I've been assigned to work on this project, and I'm not sure where to start.
|
||||
-->
|
||||
<!-- (Audio) Sophie: Hey Brian, I've been assigned to work on this project, and I'm not sure where to start. -->
|
||||
|
||||
# --description--
|
||||
|
||||
The word `assign` means to give someone a particular task or responsibility. For example, when your manager gives you a task, they are assigning work for you to do.
|
||||
|
||||
In this task, you will fill in the blanks with key words from Sophie's statement.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
@@ -53,3 +48,51 @@ Sophie is expressing uncertainty about the starting point of her task.
|
||||
### --feedback--
|
||||
|
||||
Sophie is looking for a beginning or initial step in her new assignment.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 3.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Hey, Brian, I've been assigned to work on this project, and I'm not sure where to start.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 19
|
||||
dashedName: task-2
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Hey Brian, I've been assigned to work on this project, and I'm not sure where to start.
|
||||
-->
|
||||
<!-- (Audio) Sophie: Hey Brian, I've been assigned to work on this project, and I'm not sure where to start. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -51,3 +48,51 @@ Sophie's uncertainty isn't about the project's deadline but about how to begin h
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 3.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Hey, Brian, I've been assigned to work on this project, and I'm not sure where to start.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 22
|
||||
dashedName: task-3
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Question: Could you help me understand how we should document the code?
|
||||
-->
|
||||
<!-- (Audio) Sophie: Could you help me understand how we should document the code? -->
|
||||
|
||||
# --description--
|
||||
|
||||
In this task, you'll fill in the blanks to understand the importance of asking questions about specific practices, like documenting code.
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -35,3 +32,51 @@ This word is used to ask about the method or way something should be done.
|
||||
### --feedback--
|
||||
|
||||
It means to write explanations and comments in code, making the code easier to understand for others or for future reference.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 6.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.46,
|
||||
"dialogue": {
|
||||
"text": "Could you help me understand how we should document the code?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 3.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-4
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Could you help me understand how we should document the code?
|
||||
-->
|
||||
<!-- (Audio) Sophie: Could you help me understand how we should document the code? -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task aims to check your understanding of a request for help in understanding code documentation. Documenting code is the practice of writing clear explanations within the code to help others understand it better.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ The request is for help in understanding how to do it, not for finding someone e
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 6.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.46,
|
||||
"dialogue": {
|
||||
"text": "Could you help me understand how we should document the code?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 3.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -7,7 +7,7 @@ dashedName: task-5
|
||||
|
||||
# --description--
|
||||
|
||||
The word `clear` is used in many contexts. In documentation, `clear` means easy to understand. A `clear` explanation is simple, straightforward, and easy to follow. Understanding different meanings of `clear` can help distinguish its use in various contexts.
|
||||
The word `clear` is used in many contexts. In documentation, `clear` means easy to understand. A `clear` explanation is simple, straightforward, and easy to follow.
|
||||
|
||||
# --question--
|
||||
|
||||
|
||||
@@ -7,13 +7,13 @@ dashedName: task-6
|
||||
|
||||
# --description--
|
||||
|
||||
A README file is an important part of many projects, especially in software development. It is often the first document people see when they look at a project. A README explains what the project is about, how to use it, and sometimes how to contribute to it. Understanding what a README file is used for is crucial in the context of project documentation.
|
||||
A `README` file is an important part of many projects, especially in software development. It is often the first document people see when they look at a project. A `README` explains what the project is about, how to use it, and sometimes how to contribute to it. Understanding what a `README` file is used for is crucial in the context of project documentation.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What is a README file commonly used for in a project?
|
||||
What is a `README` file commonly used for in a project?
|
||||
|
||||
## --answers--
|
||||
|
||||
@@ -21,7 +21,7 @@ Storing code
|
||||
|
||||
### --feedback--
|
||||
|
||||
While code is an integral part of a project, the README file is not used for storing code but for providing information about the project.
|
||||
While code is an integral part of a project, the `README` file is not used for storing code but for providing information about the project.
|
||||
|
||||
---
|
||||
|
||||
@@ -33,7 +33,7 @@ Contact information
|
||||
|
||||
### --feedback--
|
||||
|
||||
Even though contact information can be included, the primary purpose of a README is to give instructions and information about the project, not just contact details.
|
||||
Even though contact information can be included, the primary purpose of a `README` is to give instructions and information about the project, not just contact details.
|
||||
|
||||
---
|
||||
|
||||
@@ -41,7 +41,7 @@ Log of changes
|
||||
|
||||
### --feedback--
|
||||
|
||||
A log of changes, often called a changelog, is typically separate from a README. The README focuses on introducing and explaining the project.
|
||||
A log of changes, often called a changelog, is typically separate from a `README`. The `README` focuses on introducing and explaining the project.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ A `main folder` is the primary folder in which a project or a set of files is st
|
||||
|
||||
A `subfolder` is like a smaller drawer inside the top one, located within another folder.
|
||||
|
||||
For example, in a project called `MyProject`, the root directory would be the `MyProject` folder, and any folder inside it, like `Images`, would be a subfolder.
|
||||
For example, in a project called `MyProject`, the `root directory` would be the `MyProject` folder, and any folder inside it, like `Images`, would be a `subfolder`.
|
||||
|
||||
# --question--
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ dashedName: task-9
|
||||
|
||||
The phrase `set up` means to prepare or arrange something for use. In the context of a project or technology, it often refers to the process of getting a system, software, or equipment ready to operate.
|
||||
|
||||
For example, `setting up` a computer might involve installing software and connecting it to the internet, just as `setting up` a project might involve preparing files and directories.
|
||||
For example, `setting up a computer` might involve installing software and connecting it to the internet, just as `setting up a project` might involve preparing files and directories.
|
||||
|
||||
# --question--
|
||||
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-10
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Of course. The first thing you should do is create a clear README file in the project's root directory. This file should contain information about the project, its purpose, and how to set it up.
|
||||
-->
|
||||
<!-- (Audio) Brian: Of course. The first thing you should do is create a clear README file in the project's root directory. -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task is to test your understanding of Brian's advice to Sophie about starting her work on a project.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ Brian's advice is about documentation, not researching other projects at this st
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 7.5,
|
||||
"finishTimestamp": 12.96
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.46,
|
||||
"dialogue": {
|
||||
"text": "Of course. The first thing you should do is create a clear README file that's in the project's root directory.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,15 +5,11 @@ challengeType: 19
|
||||
dashedName: task-11
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Hey Brian, I've been assigned to work on this project, and I'm not sure where to start.
|
||||
Brian: Of course. The first thing you should do is create a clear README file in the project's root directory. This file should contain information about the project, its purpose, and how to set it up.
|
||||
-->
|
||||
<!-- (Audio) Brian: Of course. The first thing you should do is create a clear README file in the project's root directory. This file should contain information about the project, its purpose, and how to set it up. -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task tests your understanding of the details that Brian suggests including in a README file. Knowing what information to include in project documentation is vital for clarity and efficiency in project management and software development.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -52,3 +48,60 @@ Brian emphasizes the project overview and setup, not specific code examples or p
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 7.5,
|
||||
"finishTimestamp": 18.3
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.46,
|
||||
"dialogue": {
|
||||
"text": "Of course. The first thing you should do is create a clear README file that's in the project's root directory.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 7,
|
||||
"finishTime": 11.8,
|
||||
"dialogue": {
|
||||
"text": "This file should contain information about the project, its purpose, and how to set it up.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 12.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-12
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Got it. What else should I include in my README?
|
||||
-->
|
||||
<!-- (Audio) Sophie: Got it. What else should I include in my README? -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -28,7 +25,7 @@ For example, in a meeting, someone might say, `Did you get it?` and you can repl
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sophie uses `Got it` to confirm that she has understood what was previously explained.
|
||||
Sophie uses this word to confirm that she has understood what was previously explained.
|
||||
|
||||
---
|
||||
|
||||
@@ -36,4 +33,52 @@ Sophie uses `Got it` to confirm that she has understood what was previously expl
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sophie's use of `else` here is asking for additional information or items to include.
|
||||
Sophie is asking for additional information or items to include.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 18.72,
|
||||
"finishTimestamp": 20.8
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.08,
|
||||
"dialogue": {
|
||||
"text": "Got it. What else should I include in my README?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 3.58
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-13
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Got it. What else should I include in my README?
|
||||
-->
|
||||
<!-- (Audio) Sophie: Got it. What else should I include in my README? -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ Sophie is asking for suggestions on what additional information to include in th
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 18.72,
|
||||
"finishTimestamp": 20.8
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.08,
|
||||
"dialogue": {
|
||||
"text": "Got it. What else should I include in my README?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 3.58
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -7,13 +7,13 @@ dashedName: task-14
|
||||
|
||||
# --description--
|
||||
|
||||
In English, when a noun ending in `y` becomes plural, the `y` often changes to `ies.` This rule is particularly useful in technology contexts where certain terms frequently end in `y.`
|
||||
When a noun ending in `y` becomes plural, the `y` often changes to `ies.` This rule is particularly useful in technology contexts where certain terms frequently end in `y.`
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
How do you form the plural of technology-related nouns ending in `y`?
|
||||
How do you form the plural of nouns ending in `y`?
|
||||
|
||||
## --answers--
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ dashedName: task-16
|
||||
|
||||
# --description--
|
||||
|
||||
The phrase `Anyone who` is used to refer to any person who meets a specific condition or requirement.
|
||||
`Anyone who` is used to refer to any person who meets a specific condition or requirement.
|
||||
|
||||
In technology, it's often used to describe people with certain skills or knowledge. For example, `Anyone who understands JavaScript can modify this script.`
|
||||
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 22
|
||||
dashedName: task-17
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should list the project dependencies so that anyone who wants to work on it knows what they need.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should list the project dependencies so that anyone who wants to work on it knows what they need. -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task applies the vocabulary and concepts you've learned in context. Fill in the blanks in a summary of Brian's advice.
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -26,7 +23,7 @@ This task applies the vocabulary and concepts you've learned in context. Fill in
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian is talking about listing `dependencies,` which are the necessary components or resources for the project.
|
||||
These are the necessary components or resources for the project.
|
||||
|
||||
---
|
||||
|
||||
@@ -51,3 +48,51 @@ It refers to any person who might be interested in or responsible for working on
|
||||
### --feedback--
|
||||
|
||||
It is used here to introduce a defining clause, specifying the group of people as those wanting to work on the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.22,
|
||||
"finishTimestamp": 26.38
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.16,
|
||||
"dialogue": {
|
||||
"text": "You should list the project dependencies so that anyone who wants to work on it knows what they need.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.66
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-18
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should list the project dependencies so that anyone who wants to work on it knows what they need.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should list the project dependencies so that anyone who wants to work on it knows what they need. -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ Tracking coding progress is important, but the reason Brian gives is to inform p
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.22,
|
||||
"finishTimestamp": 26.38
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.16,
|
||||
"dialogue": {
|
||||
"text": "You should list the project dependencies so that anyone who wants to work on it knows what they need.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.66
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-19
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Then specify how to run the code and any other essential setup instructions.
|
||||
-->
|
||||
<!-- (Audio) Brian: Then specify how to run the code and any other essential setup instructions. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -47,3 +44,51 @@ This word in this context means to start or execute the code. Brian wants instru
|
||||
### --feedback--
|
||||
|
||||
This word refers to the process of arranging or preparing something. Here, it relates to the essential preparation instructions for the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 26.38,
|
||||
"finishTimestamp": 30.96
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.58,
|
||||
"dialogue": {
|
||||
"text": "Then specify how to run the code and any other essential setup instructions.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-20
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Also, mention the coding conventions we follow in this project.
|
||||
-->
|
||||
<!-- (Audio) Brian: Also, mention coding conventions we follow in this project. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -20,7 +17,7 @@ A `convention` is like a rule or way that most people agree to do things, especi
|
||||
|
||||
## --sentence--
|
||||
|
||||
`_, mention the coding _ we _ in this project.`
|
||||
`_, mention coding _ we _ in this project.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
@@ -45,3 +42,51 @@ These are the usual rules or ways people agree to do things, like writing code i
|
||||
### --feedback--
|
||||
|
||||
It means to use or do what the coding rules or ways say in the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 31.44,
|
||||
"finishTimestamp": 34.96
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.52,
|
||||
"dialogue": {
|
||||
"text": "Also, mention coding conventions we follow in this project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 5.12
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-21
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should list the project dependencies so that anyone who wants to work on it knows what they need. Then specify how to run the code and any other essential setup instructions. Also, mention coding conventions we follow in this project.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should list the project dependencies so that anyone who wants to work on it knows what they need. Then specify how to run the code and any other essential setup instructions. Also, mention coding conventions we follow in this project. -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task tests your understanding of the list of instructions Brian gives to Sophie. Being able to summarize and recall instructions is important for effective communication and collaboration in project work.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,78 @@ Brian's focus is on documenting existing aspects of the project, not creating ne
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.22,
|
||||
"finishTimestamp": 34.96
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.12,
|
||||
"dialogue": {
|
||||
"text": "You should list the project dependencies",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 3.12,
|
||||
"finishTime": 6.16,
|
||||
"dialogue": {
|
||||
"text": "so that anyone who wants to work on it knows what they need.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 6.16,
|
||||
"finishTime": 10.74,
|
||||
"dialogue": {
|
||||
"text": "Then specify how to run the code and any other essential setup instructions.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 11.82,
|
||||
"finishTime": 14.74,
|
||||
"dialogue": {
|
||||
"text": "Also, mention coding conventions we follow in this project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 15.24
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,18 +5,13 @@ challengeType: 22
|
||||
dashedName: task-22
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Thanks. I'll make sure to follow your instructions.
|
||||
-->
|
||||
<!-- (Audio) Sophie: Thanks. I'll make sure to follow your instructions. -->
|
||||
|
||||
# --description--
|
||||
|
||||
`Make` in this context means to ensure or see to it.
|
||||
`Make sure` means to verify or confirm that something is done correctly or that a condition is met. It involves taking the necessary steps to ensure accuracy or completion. For example, `Please make sure you turn off the lights before you leave.`
|
||||
|
||||
`Follow` means to adhere to or go along with.
|
||||
|
||||
`Instructions` are directions or orders given by someone.
|
||||
`Follow instructions` means to adhere to the directions or guidelines provided for completing a task. It involves doing each step in the specified order and manner. An example is `follow the instructions on the box to assemble the table`.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -47,3 +42,51 @@ It means Sophie plans to adhere to or go along with the instructions given.
|
||||
### --feedback--
|
||||
|
||||
It refers to the directions or guidance that Brian has provided.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 35.72,
|
||||
"finishTimestamp": 37.78
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.06,
|
||||
"dialogue": {
|
||||
"text": "Thanks, I'll make sure to follow your instructions.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 3.56
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,20 +5,17 @@ challengeType: 22
|
||||
dashedName: task-23
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Entire dialogue
|
||||
-->
|
||||
<!-- (Audio) The whole dialogue -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task is a summary exercise using key vocabulary from the previous challenges.
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Sophie has been _ to work on a project and needs to know how to _ the code. Brian suggests creating a README file in the _ _, listing _, specifying how to _ the code, and mentioning the coding _ they _. Sophie thanks Brian and _ sure she will follow his _.`
|
||||
`Sophie has been _ to work on a project and needs to know how to _ the code. Brian suggests creating a README file in the _ _, listing _, specifying how to _ the code, and mentioning the coding _ they _. Sophie thanks Brian and will _ sure she follows his _.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
@@ -86,7 +83,7 @@ It means to adhere to or go along with the given guidance.
|
||||
|
||||
---
|
||||
|
||||
`makes`
|
||||
`make`
|
||||
|
||||
### --feedback--
|
||||
|
||||
@@ -99,3 +96,131 @@ In this context, it is about ensuring or seeing to it that something is done.
|
||||
### --feedback--
|
||||
|
||||
These are the directions or guidance provided by Brian.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-1.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Hey, Brian, I've been assigned to work on this project, and I'm not sure where to start.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 5.48,
|
||||
"finishTime": 7.94,
|
||||
"dialogue": {
|
||||
"text": "Could you help me understand how we should document the code?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 8.5,
|
||||
"finishTime": 13.96,
|
||||
"dialogue": {
|
||||
"text": "Of course. The first thing you should do is create a clear README file that's in the project's root directory.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 14.5,
|
||||
"finishTime": 19.3,
|
||||
"dialogue": {
|
||||
"text": "This file should contain information about the project, its purpose, and how to set it up.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 19.72,
|
||||
"finishTime": 21.8,
|
||||
"dialogue": {
|
||||
"text": "Got it. What else should I include in my README?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 22.22,
|
||||
"finishTime": 27.38,
|
||||
"dialogue": {
|
||||
"text": "You should list the project dependencies so that anyone who wants to work on it knows what they need.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 27.38,
|
||||
"finishTime": 31.96,
|
||||
"dialogue": {
|
||||
"text": "Then specify how to run the code and any other essential setup instructions.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 33.04,
|
||||
"finishTime": 35.96,
|
||||
"dialogue": {
|
||||
"text": "Also, mention coding conventions we follow in this project.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 36.92,
|
||||
"finishTime": 38.78,
|
||||
"dialogue": {
|
||||
"text": "Thanks, I'll make sure to follow your instructions.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 39.28
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 39.78
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
id: 65e86cac39492642332416e9
|
||||
videoId: nLDychdBwUg
|
||||
title: "Dialogue 2: Adding Comments to Code"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-2-adding-comments-to-code
|
||||
@@ -8,8 +7,136 @@ dashedName: dialogue-2-adding-comments-to-code
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video above to understand the context of the upcoming lessons.
|
||||
Watch the video to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I'm working on this code and I think it's a good idea to add comments.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 5.22,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How should I write comments in the code?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 7.44,
|
||||
"finishTime": 12.36,
|
||||
"dialogue": {
|
||||
"text": "Great idea. To write comments, you simply need to use double slashes to start a comment.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 12.98,
|
||||
"finishTime": 17.56,
|
||||
"dialogue": {
|
||||
"text": "Then, you can describe what the code does so that other people can understand it, too.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 18.36,
|
||||
"finishTime": 21.94,
|
||||
"dialogue": {
|
||||
"text": "And what should I comment on? Are there any specific things I should focus on?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 22.34,
|
||||
"finishTime": 26.24,
|
||||
"dialogue": {
|
||||
"text": "You should comment on any complex or tricky parts of your code.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 26.24,
|
||||
"finishTime": 30.92,
|
||||
"dialogue": {
|
||||
"text": "You can also explain what certain functions do and clarify the purpose of variables.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 31.36,
|
||||
"finishTime": 34.82,
|
||||
"dialogue": {
|
||||
"text": "Try to ensure that your comments are clear and concise.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 35.66,
|
||||
"finishTime": 38.3,
|
||||
"dialogue": {
|
||||
"text": "I appreciate your help. I'll start adding comments to the code.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 38.8
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 39.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-24
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: I'm working on this code, and I think it's a good idea to add comments. How should I write comments in the code?
|
||||
-->
|
||||
<!-- (Audio) Sophie: I'm working on this code, and I think it's a good idea to add comments. How should I write comments in the code? -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,60 @@ Sophie's statement is about adding comments to the code, not about fixing bugs.
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 5.9
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I'm working on this code and I think it's a good idea to add comments.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 5.22,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How should I write comments in the code?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 7.4
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-25
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Great idea. To write comments, you simply need to use double slashes to start a comment.
|
||||
-->
|
||||
<!-- (Audio) Brian: Great idea. To write comments, you simply need to use double slashes to start a comment. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -16,13 +13,13 @@ In this task, you'll learn the difference between `simple` and `simply`, and und
|
||||
|
||||
`Simple` is an adjective meaning easy or not complicated, like `a simple task`. `Simply` is an adverb, meaning in a simple manner, like `doing something simply`.
|
||||
|
||||
`Double` means two of something, and `slashes` are the `/` symbols used in writing. You add `es` to make `slash` plural because words ending in `sh` form their plurals by adding `es,` like in `dishes` or `brushes`.
|
||||
`Double` means two of something. And `slashes` are the `/` symbols used in writing. You add `es` to make `slash` plural because words ending in `sh` form their plurals by adding `es,` like in `dishes` or `brushes`.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`To write comments, you _ need to use _ _ to start a comment.`
|
||||
`Great idea. To write comments, you _ need to use _ _ to start a comment.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
@@ -47,3 +44,51 @@ It refers to using two of something. In this context, it means using two slashes
|
||||
### --feedback--
|
||||
|
||||
These are the `/` symbols. For words ending in `sh` you should add `es` for the plural.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.24,
|
||||
"finishTimestamp": 11.36
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.12,
|
||||
"dialogue": {
|
||||
"text": "Great idea. To write comments, you simply need to use double slashes to start a comment.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 22
|
||||
dashedName: task-26
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Then, you can describe what the code does so that other people can understand it, too.
|
||||
-->
|
||||
<!-- (Audio) Brian: Then, you can describe what the code does so that other people can understand it, too. -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -43,3 +40,51 @@ It refers to the function or action of the code. Brian is talking about explaini
|
||||
### --feedback--
|
||||
|
||||
This word means to comprehend or grasp the meaning. Brian encourages explaining the code so others can grasp its purpose.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 11.98,
|
||||
"finishTimestamp": 16.56
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.58,
|
||||
"dialogue": {
|
||||
"text": "Then, you can describe what the code does so that other people can understand it, too.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-27
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Great idea. To write comments, you simply need to use double slashes to start a comment. Then, you can describe what the code does so that other people can understand it, too.
|
||||
-->
|
||||
<!-- (Audio) Brian: Great idea. To write comments, you simply need to use double slashes to start a comment. Then, you can describe what the code does so that other people can understand it, too. -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task assesses your understanding of Brian's instructions on writing comments in code. Being able to correctly interpret instructions on coding practices is crucial for effective programming and collaboration.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,60 @@ Brian encourages writing comments using double slashes to help others understand
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.24,
|
||||
"finishTimestamp": 16.56
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.12,
|
||||
"dialogue": {
|
||||
"text": "Great idea. To write comments, you simply need to use double slashes to start a comment.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 6.74,
|
||||
"finishTime": 11.32,
|
||||
"dialogue": {
|
||||
"text": "Then, you can describe what the code does so that other people can understand it, too.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 11.82
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-28
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: And what should I comment on? Are there any specific things I should focus on?
|
||||
-->
|
||||
<!-- (Audio) Sophie: And what should I comment on? Are there any specific things I should focus on? -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -45,3 +42,51 @@ This word is used to ask about the existence of unspecified items or points to c
|
||||
### --feedback--
|
||||
|
||||
This word is used similarly to the first, indicating the subject or area of focus.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 17.36,
|
||||
"finishTimestamp": 20.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.58,
|
||||
"dialogue": {
|
||||
"text": "And what should I comment on? Are there any specific things I should focus on?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 5.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-29
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: And what should I comment on? Are there any specific things I should focus on?
|
||||
-->
|
||||
<!-- (Audio) Sophie: And what should I comment on? Are there any specific things I should focus on? -->
|
||||
|
||||
# --description--
|
||||
|
||||
Understanding questions in a technical context is crucial for effective communication and collaboration.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ What topics or aspects she should comment on in the code
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 17.36,
|
||||
"finishTimestamp": 20.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.58,
|
||||
"dialogue": {
|
||||
"text": "And what should I comment on? Are there any specific things I should focus on?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 5.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-30
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should comment on any complex or tricky parts of your code.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should comment on any complex or tricky parts of your code. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -35,3 +32,51 @@ It means to make notes or explain something. Brian suggests explaining difficult
|
||||
### --feedback--
|
||||
|
||||
It describes something that is not easy to understand or do. Brian is advising to note down the more challenging parts of the code.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.34,
|
||||
"finishTimestamp": 25.24
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.9,
|
||||
"dialogue": {
|
||||
"text": "You should comment on any complex or tricky parts of your code.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 5.4
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,26 +5,15 @@ challengeType: 22
|
||||
dashedName: task-31
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You can also explain what certain functions do, and clarify the purpose of variables.
|
||||
-->
|
||||
<!-- (Audio) Brian: You can also explain what certain functions do, and clarify the purpose of variables. -->
|
||||
|
||||
# --description--
|
||||
|
||||
`Clarify` means to make something clear or easier to understand. For instance, you might `clarify` a complex idea by explaining it in simpler terms.
|
||||
`Clarify` means to make something clear or easier to understand. You might `clarify` a complex idea by explaining it in simpler terms. For example, `He clarified the instructions by providing a step-by-step guide.`
|
||||
|
||||
`Functions` in programming are sets of instructions that perform a specific task.
|
||||
`Function` in programming is a set of instructions that perform a specific task. For instance, `The "calculateTotal" function adds up all the prices.`
|
||||
|
||||
A `variable` is like a box where you can store information or data in a computer program. You can change what's inside the box, or `variable`, as your program runs. It's a way to keep track of and use data in your code.
|
||||
|
||||
Examples:
|
||||
|
||||
`He clarified the instructions by providing a step-by-step guide.`
|
||||
|
||||
`The "calculateTotal" function adds up all the prices.`
|
||||
|
||||
`The variable "score" keeps track of the player's points.`
|
||||
A `variable` is like a box where you can store information or data in a computer program. You can change what's inside the box, or `variable`, as your program runs. It's a way to keep track of and use data in your code. For example, `The variable "score" keeps track of the player's points.`
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -55,3 +44,51 @@ It means to make something easier to understand. Brian is advising to make the r
|
||||
### --feedback--
|
||||
|
||||
They hold and store data in code. Brian recommends explaining what these are used for in the code.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 25.24,
|
||||
"finishTimestamp": 29.92
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.68,
|
||||
"dialogue": {
|
||||
"text": "You can also explain what certain functions do and clarify the purpose of variables.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.18
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-32
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Try to ensure that your comments are clear and concise.
|
||||
-->
|
||||
<!-- (Audio) Brian: Try to ensure that your comments are clear and concise. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -47,3 +44,51 @@ This word in this context means easy to understand. Brian advises that the comme
|
||||
### --feedback--
|
||||
|
||||
This word means brief and to the point. Brian is suggesting that the comments should be short and not overly detailed.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 30.36,
|
||||
"finishTimestamp": 33.82
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.46,
|
||||
"dialogue": {
|
||||
"text": "Try to ensure that your comments are clear and concise.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 4.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-33
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should comment on any complex or tricky parts of your code. You can also explain what certain functions do, and clarify the purpose of variables. Try to ensure that your comments are clear and concise.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should comment on any complex or tricky parts of your code. You can also explain what certain functions do, and clarify the purpose of variables. Try to ensure that your comments are clear and concise. -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,69 @@ Brian recommends explaining functions and clarifying variables, not avoiding com
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.34,
|
||||
"finishTimestamp": 33.82
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.9,
|
||||
"dialogue": {
|
||||
"text": "You should comment on any complex or tricky parts of your code.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 4.9,
|
||||
"finishTime": 9.58,
|
||||
"dialogue": {
|
||||
"text": "You can also explain what certain functions do and clarify the purpose of variables.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 10.02,
|
||||
"finishTime": 13.48,
|
||||
"dialogue": {
|
||||
"text": "Try to ensure that your comments are clear and concise.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 13.98
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-34
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: I appreciate your help. I'll start adding comments to the code.
|
||||
-->
|
||||
<!-- (Audio) Sophie: I appreciate your help. I'll start adding comments to the code. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -37,3 +34,51 @@ This word is used to express gratitude or thankfulness. Sophie is thanking Brian
|
||||
### --feedback--
|
||||
|
||||
It means to put something new into something else. Sophie is planning to put new comments into the code.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 34.46,
|
||||
"finishTimestamp": 37.3
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.84,
|
||||
"dialogue": {
|
||||
"text": "I appreciate your help. I'll start adding comments to the code.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 4.34
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 22
|
||||
dashedName: task-35
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Entire dialogue
|
||||
-->
|
||||
<!-- (Audio) The whole dialogue -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task involves summarizing the dialogue between Sophie and Brian using key terms.
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -34,7 +31,7 @@ These are notes in code that explain what it does. This is what Sophie wants to
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian advises focusing on `complex` parts of the code, meaning the more difficult or complicated areas.
|
||||
Brian advises focusing on more difficult or complicated parts of the code.
|
||||
|
||||
---
|
||||
|
||||
@@ -67,3 +64,131 @@ It means being thankful for Brian's advice and guidance on commenting.
|
||||
### --feedback--
|
||||
|
||||
It means putting comments into the code.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-2.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I'm working on this code and I think it's a good idea to add comments.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 5.22,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How should I write comments in the code?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 7.44,
|
||||
"finishTime": 12.36,
|
||||
"dialogue": {
|
||||
"text": "Great idea. To write comments, you simply need to use double slashes to start a comment.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 12.98,
|
||||
"finishTime": 17.56,
|
||||
"dialogue": {
|
||||
"text": "Then, you can describe what the code does so that other people can understand it, too.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 18.36,
|
||||
"finishTime": 21.94,
|
||||
"dialogue": {
|
||||
"text": "And what should I comment on? Are there any specific things I should focus on?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 22.34,
|
||||
"finishTime": 26.24,
|
||||
"dialogue": {
|
||||
"text": "You should comment on any complex or tricky parts of your code.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 26.24,
|
||||
"finishTime": 30.92,
|
||||
"dialogue": {
|
||||
"text": "You can also explain what certain functions do and clarify the purpose of variables.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 31.36,
|
||||
"finishTime": 34.82,
|
||||
"dialogue": {
|
||||
"text": "Try to ensure that your comments are clear and concise.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 35.66,
|
||||
"finishTime": 38.3,
|
||||
"dialogue": {
|
||||
"text": "I appreciate your help. I'll start adding comments to the code.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 38.8
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 39.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
id: 65e943b74900112d64038331
|
||||
videoId: nLDychdBwUg
|
||||
title: "Dialogue 3: Version Control and Documenting Changes"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-3-version-control-and-documenting-changes
|
||||
@@ -8,8 +7,145 @@ dashedName: dialogue-3-version-control-and-documenting-changes
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video above to understand the context of the upcoming lessons.
|
||||
Watch the video to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.4,
|
||||
"dialogue": {
|
||||
"text": "I see that we're using Git for version control.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 3.92,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How do I document code changes when I make updates or fixes?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 7.6,
|
||||
"finishTime": 12,
|
||||
"dialogue": {
|
||||
"text": "Good question. When you make changes, you should use descriptive commit messages.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 12.44,
|
||||
"finishTime": 15.1,
|
||||
"dialogue": {
|
||||
"text": "Start your message with a verb in the imperative form",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 15.1,
|
||||
"finishTime": 20.7,
|
||||
"dialogue": {
|
||||
"text": "like fix, add, or update followed by a brief description of what you did.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 21.14,
|
||||
"finishTime": 23.92,
|
||||
"dialogue": {
|
||||
"text": "That sounds straightforward. Anything else I should keep in mind?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 24.32,
|
||||
"finishTime": 27.12,
|
||||
"dialogue": {
|
||||
"text": "You should also reference issues in your commit message",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 27.12,
|
||||
"finishTime": 29.44,
|
||||
"dialogue": {
|
||||
"text": "if you're working on a task related to an issue.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 29.88,
|
||||
"finishTime": 33.67,
|
||||
"dialogue": {
|
||||
"text": "It helps in tracking progress and understanding the context of changes.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 34.28,
|
||||
"finishTime": 37.1,
|
||||
"dialogue": {
|
||||
"text": "Thanks for the clarification. I'll make sure to follow these steps.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 37.6
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 38.1
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 22
|
||||
dashedName: task-36
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: I see that we're using Git for version control. How do I document code changes when I make updates or fixes?
|
||||
-->
|
||||
<!-- (Audio) Sophie: I see that we're using Git for version control. How do I document code changes when I make updates or fixes? -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -43,3 +40,60 @@ This word is used to ask about the method or process of documenting code changes
|
||||
### --feedback--
|
||||
|
||||
This word refers to the timing, in this case, asking about the moment of making updates or fixes to document changes.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 5.9
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.4,
|
||||
"dialogue": {
|
||||
"text": "I see that we're using Git for version control.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 3.92,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How do I document code changes when I make updates or fixes?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 7.4
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-37
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: I see that we're using Git for version control. How do I document code changes when I make updates or fixes?
|
||||
-->
|
||||
<!-- (Audio) Sophie: I see that we're using Git for version control. How do I document code changes when I make updates or fixes? -->
|
||||
|
||||
# --description--
|
||||
|
||||
Let’s practice!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,60 @@ Her question focuses on documenting updates or fixes, not on creating a new repo
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 5.9
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.4,
|
||||
"dialogue": {
|
||||
"text": "I see that we're using Git for version control.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 3.92,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How do I document code changes when I make updates or fixes?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 7.4
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,18 +5,15 @@ challengeType: 22
|
||||
dashedName: task-38
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Good question. When you make changes, you should use descriptive commit messages.
|
||||
-->
|
||||
<!-- (Audio) Brian: Good question. When you make changes, you should use descriptive commit messages. -->
|
||||
|
||||
# --description--
|
||||
|
||||
`Changes` in this context means modifications or edits made in the code.
|
||||
|
||||
`Descriptive` means giving a lot of details or information.
|
||||
`Descriptive` means giving details about how something looks, feels, sounds, smells, or tastes. It is an adjective used to provide more information about a noun, making the description more vivid and clear. For example, in the sentence `she wears a beautiful dress`, the word `beautiful` is `descriptive` because it tells listeners more about the dress.
|
||||
|
||||
A `message` is a piece of information or communication that someone sends to another person. It can be written, spoken, or even sent through email or text. It's a way to share thoughts, information, or feelings with someone else.
|
||||
A `message` is a piece of information or communication that someone sends to another person. It can be written, spoken, or even sent through email or text.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -55,3 +52,51 @@ This word indicates that the commit messages should be detailed and informative.
|
||||
### --feedback--
|
||||
|
||||
In this context, it means the notes or comments written to explain what was done in a commit.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.6,
|
||||
"finishTimestamp": 11
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.4,
|
||||
"dialogue": {
|
||||
"text": "Good question. When you make changes, you should use descriptive commit messages.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 5.9
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-39
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Good question. When you make changes, you should use descriptive commit messages.
|
||||
-->
|
||||
<!-- (Audio) Brian: Good question. When you make changes, you should use descriptive commit messages. -->
|
||||
|
||||
# --description--
|
||||
|
||||
Practice time!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ Brian suggests documenting changes with commit messages, not reverting them.
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.6,
|
||||
"finishTimestamp": 11
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.4,
|
||||
"dialogue": {
|
||||
"text": "Good question. When you make changes, you should use descriptive commit messages.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 5.9
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,16 +5,13 @@ challengeType: 22
|
||||
dashedName: task-40
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Start your message with a verb in the imperative form, like `Fix`, `Add`, or `Update`, followed by a brief description of what you did.
|
||||
-->
|
||||
<!-- (Audio) Brian: Start your message with a verb in the imperative form, like `Fix`, `Add`, or `Update`, followed by a brief description of what you did. -->
|
||||
|
||||
# --description--
|
||||
|
||||
The `imperative` form is a command or instruction. For example, `Close the door.`
|
||||
|
||||
`Brief` means short and to the point. An example is, `He gave a brief explanation.`
|
||||
`Brief` means short and to the point. For instance, `He gave a brief explanation.`
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -45,3 +42,51 @@ It means short and concise. Brian advises keeping the description of the action
|
||||
### --feedback--
|
||||
|
||||
This word is used to refer to the action that was completed. Brian is talking about describing what action was done in the code.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 11.24,
|
||||
"finishTimestamp": 19.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 9.46,
|
||||
"dialogue": {
|
||||
"text": "Start your message with a verb in the imperative form like fix, add, or update followed by a brief description of what you did.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 9.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-41
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Good question. When you make changes, you should use descriptive commit messages. Start your message with a verb in the imperative form, like `Fix`, `Add`, or `Update`, followed by a brief description of what you did.
|
||||
-->
|
||||
<!-- (Audio) Brian: Good question. When you make changes, you should use descriptive commit messages. Start your message with a verb in the imperative form, like `Fix`, `Add`, or `Update`, followed by a brief description of what you did. -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task tests your comprehension of Brian's advice on how to write commit messages in Git.
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,69 @@ Brian actually suggests starting commit messages with a verb in the imperative f
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.6,
|
||||
"finishTimestamp": 19.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.4,
|
||||
"dialogue": {
|
||||
"text": "Good question. When you make changes, you should use descriptive commit messages.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 5.84,
|
||||
"finishTime": 8.5,
|
||||
"dialogue": {
|
||||
"text": "Start your message with a verb in the imperative form",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 8.5,
|
||||
"finishTime": 14.1,
|
||||
"dialogue": {
|
||||
"text": "like fix, add, or update followed by a brief description of what you did.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 14.6
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-42
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: That sounds straightforward. Anything else I should keep in mind?
|
||||
-->
|
||||
<!-- (Audio) Sophie: That sounds straightforward. Anything else I should keep in mind? -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -18,7 +15,7 @@ Sophie: That sounds straightforward. Anything else I should keep in mind?
|
||||
|
||||
`Straightforward` combines these ideas to mean something simple and easy to understand, without complexity. For instance, `The instructions were straightforward and easy to follow.`
|
||||
|
||||
`Keep` means to continue to have or hold. An example is `Keep the door closed.`
|
||||
`Keep` means to continue to have or hold. An example is `to keep the door closed`.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -41,3 +38,51 @@ This word describes something that is simple and easy to understand. Sophie find
|
||||
### --feedback--
|
||||
|
||||
This word in this context means to continue to consider or remember. Sophie is asking if there's anything else important to remember.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.14,
|
||||
"finishTimestamp": 22.92
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.78,
|
||||
"dialogue": {
|
||||
"text": "That sounds straightforward. Anything else I should keep in mind?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 4.28
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-43
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: That sounds straightforward. Anything else I should keep in mind?
|
||||
-->
|
||||
<!-- (Audio) Sophie: That sounds straightforward. Anything else I should keep in mind? -->
|
||||
|
||||
# --description--
|
||||
|
||||
Practice time!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -51,3 +48,51 @@ Sophie's question is directly related to the current topic of commit messages an
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.14,
|
||||
"finishTimestamp": 22.92
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.78,
|
||||
"dialogue": {
|
||||
"text": "That sounds straightforward. Anything else I should keep in mind?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 4.28
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-44
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should also reference issues in your commit messages if you're working on a task related to an issue.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should also reference issues in your commit messages if you're working on a task related to an issue. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -45,3 +42,51 @@ It is about being connected to something. Here, it refers to tasks that are conn
|
||||
### --feedback--
|
||||
|
||||
It refers to a problem or topic, especially one that needs attention in a project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 23.32,
|
||||
"finishTimestamp": 28.44
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.12,
|
||||
"dialogue": {
|
||||
"text": "You should also reference issues in your commit message if you're working on a task related to an issue.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 6.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,10 +5,7 @@ challengeType: 22
|
||||
dashedName: task-45
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: It helps in tracking progress and understanding the context of changes.
|
||||
-->
|
||||
<!-- (Audio) Brian: It helps in tracking progress and understanding the context of changes. -->
|
||||
|
||||
# --description--
|
||||
|
||||
@@ -37,3 +34,51 @@ It is about monitoring or keeping an eye on something, such as progress in a pro
|
||||
### --feedback--
|
||||
|
||||
It means the situation or background that helps explain something, like the reasons behind changes in a project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 28.68,
|
||||
"finishTimestamp": 32.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.02,
|
||||
"dialogue": {
|
||||
"text": "It helps in tracking progress and understanding the context of changes.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 5.52
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 19
|
||||
dashedName: task-46
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: You should also reference issues in your commit messages if you're working on a task related to an issue. It helps in tracking progress and understanding the context of changes.
|
||||
-->
|
||||
<!-- (Audio) Brian: You should also reference issues in your commit messages if you're working on a task related to an issue. It helps in tracking progress and understanding the context of changes. -->
|
||||
|
||||
# --description--
|
||||
|
||||
Practice time!
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
@@ -30,7 +27,7 @@ The focus isn't on making messages longer but on providing specific information
|
||||
|
||||
---
|
||||
|
||||
Only when working on tasks related to an issue, to help track progress and understand changes
|
||||
When working on tasks related to an issue, to help track progress and understand changes
|
||||
|
||||
---
|
||||
|
||||
@@ -51,3 +48,69 @@ Referencing issues is meant for context and tracking progress, not just to indic
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 23.32,
|
||||
"finishTimestamp": 32.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.8,
|
||||
"dialogue": {
|
||||
"text": "You should also reference issues in your commit message",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 3.8,
|
||||
"finishTime": 6.12,
|
||||
"dialogue": {
|
||||
"text": "if you're working on a task related to an issue.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 6.56,
|
||||
"finishTime": 10.38,
|
||||
"dialogue": {
|
||||
"text": "It helps in tracking progress and understanding the context of changes.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"opacity": 0,
|
||||
"startTime": 10.88
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,14 +5,11 @@ challengeType: 22
|
||||
dashedName: task-47
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sophie: Thanks for the clarification. I'll make sure to follow these steps.
|
||||
-->
|
||||
<!-- (Audio) Sophie: Thanks for the clarification. I'll make sure to follow these steps. -->
|
||||
|
||||
# --description--
|
||||
|
||||
Practice time!
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
@@ -35,3 +32,51 @@ It is about making something more understandable. Sophie is thanking Brian for m
|
||||
### --feedback--
|
||||
|
||||
This word refers to the specific steps Brian mentioned. Sophie commits to following them.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 33.08,
|
||||
"finishTimestamp": 36.1
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.02,
|
||||
"dialogue": {
|
||||
"text": "Thanks for the clarification. I'll make sure to follow these steps.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"opacity": 0,
|
||||
"startTime": 4.52
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -5,20 +5,17 @@ challengeType: 22
|
||||
dashedName: task-48
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Entire dialogue
|
||||
-->
|
||||
<!-- (Audio) The whole dialogue -->
|
||||
|
||||
# --description--
|
||||
|
||||
This task involves summarizing the key points from Sophie and Brian's conversation about using Git for version control. Summarizing helps in understanding the main points of a conversation. Focus on key terms related to Git usage, commit messages, and documenting code changes.
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Sophie learns they're using Git for version control and asks how to _ code changes. Brian advises using _ commit messages, starting with an _ verb like "Fix" or "Add", followed by a _ description. He also mentions to _ issues in commit messages when related to an _. Sophie thanks Brian for the _ and commits to _ these steps.`
|
||||
`Sophie learns they're using Git for version control and asks how to _ code changes. Brian advises using _ commit messages, starting with an _ verb like "Fix" or "Add", followed by a _ description. He also says she should _ issues in commit messages when related to an _. Sophie thanks Brian for the _ and says she will _ these steps.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
@@ -83,3 +80,140 @@ It is the explanation or information that makes something clear or understandabl
|
||||
### --feedback--
|
||||
|
||||
It means to adhere to or go along with the advised steps.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "7.1-3.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.4,
|
||||
"dialogue": {
|
||||
"text": "I see that we're using Git for version control.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 3.92,
|
||||
"finishTime": 6.9,
|
||||
"dialogue": {
|
||||
"text": "How do I document code changes when I make updates or fixes?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 7.6,
|
||||
"finishTime": 12,
|
||||
"dialogue": {
|
||||
"text": "Good question. When you make changes, you should use descriptive commit messages.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 12.44,
|
||||
"finishTime": 15.1,
|
||||
"dialogue": {
|
||||
"text": "Start your message with a verb in the imperative form",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 15.1,
|
||||
"finishTime": 20.7,
|
||||
"dialogue": {
|
||||
"text": "like fix, add, or update followed by a brief description of what you did.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 21.14,
|
||||
"finishTime": 23.92,
|
||||
"dialogue": {
|
||||
"text": "That sounds straightforward. Anything else I should keep in mind?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 24.32,
|
||||
"finishTime": 27.12,
|
||||
"dialogue": {
|
||||
"text": "You should also reference issues in your commit message",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 27.12,
|
||||
"finishTime": 29.44,
|
||||
"dialogue": {
|
||||
"text": "if you're working on a task related to an issue.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"startTime": 29.88,
|
||||
"finishTime": 33.67,
|
||||
"dialogue": {
|
||||
"text": "It helps in tracking progress and understanding the context of changes.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"startTime": 34.28,
|
||||
"finishTime": 37.1,
|
||||
"dialogue": {
|
||||
"text": "Thanks for the clarification. I'll make sure to follow these steps.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Brian",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 37.6
|
||||
},
|
||||
{
|
||||
"character": "Sophie",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 38.1
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user