mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-05-26 13:01:43 -04:00
feat(curriculum): Add English tasks B1 Block 10 (#58943)
Co-authored-by: Nielda Karla <90112119+nieldakarla@users.noreply.github.com> Co-authored-by: Naomi <accounts+github@nhcarrigan.com>
This commit is contained in:
miyaliu666
@@ -1631,7 +1631,9 @@
|
||||
},
|
||||
"learn-how-to-express-agreement": {
|
||||
"title": "Learn How to Express Agreement",
|
||||
"intro": ["", ""]
|
||||
"intro": [
|
||||
"In this course, you will learn to express agreement in different professional settings."
|
||||
]
|
||||
},
|
||||
"learn-how-to-express-disagreement": {
|
||||
"title": "Learn How to Express Disagreement",
|
||||
|
||||
@@ -1,13 +1,557 @@
|
||||
{
|
||||
"name": "Learn How to Express Agreement",
|
||||
"isUpcomingChange": true,
|
||||
"isUpcomingChange": false,
|
||||
"dashedName": "learn-how-to-express-agreement",
|
||||
"order": 9,
|
||||
"superBlock": "b1-english-for-developers",
|
||||
"challengeOrder": [
|
||||
{
|
||||
"id": "6660a04ec4ec815eb81ede7c",
|
||||
"title": "Dialogue 1: I'm Tom"
|
||||
"title": "Dialogue 1: Project Planning"
|
||||
},
|
||||
{
|
||||
"id": "677bf6d81eba074172a73a2e",
|
||||
"title": "Task 1"
|
||||
},
|
||||
{
|
||||
"id": "6780284188c80df6c1483f2f",
|
||||
"title": "Task 2"
|
||||
},
|
||||
{
|
||||
"id": "67802a99de4bf605a5397ccd",
|
||||
"title": "Task 3"
|
||||
},
|
||||
{
|
||||
"id": "67802cab680a85130fd846a0",
|
||||
"title": "Task 4"
|
||||
},
|
||||
{
|
||||
"id": "678030ed8973e82d5b439ff9",
|
||||
"title": "Task 5"
|
||||
},
|
||||
{
|
||||
"id": "678033a501bb6d3e2fc0eb50",
|
||||
"title": "Task 6"
|
||||
},
|
||||
{
|
||||
"id": "67803535dcaa454865db5fd0",
|
||||
"title": "Task 7"
|
||||
},
|
||||
{
|
||||
"id": "678036b3f7eb4651f6c273c2",
|
||||
"title": "Task 8"
|
||||
},
|
||||
{
|
||||
"id": "679b6fda63e57f01cdd2a45d",
|
||||
"title": "Task 9"
|
||||
},
|
||||
{
|
||||
"id": "679b7597814cfe0657acb4f5",
|
||||
"title": "Task 10"
|
||||
},
|
||||
{
|
||||
"id": "679b72572a03cc037def37c3",
|
||||
"title": "Task 11"
|
||||
},
|
||||
{
|
||||
"id": "679b73bd4f95b4048fe6f9b9",
|
||||
"title": "Task 12"
|
||||
},
|
||||
{
|
||||
"id": "679b74ee20b7400598e672ce",
|
||||
"title": "Task 13"
|
||||
},
|
||||
{
|
||||
"id": "67a74fd46f19afe4d0aff00f",
|
||||
"title": "Task 14"
|
||||
},
|
||||
{
|
||||
"id": "67a751e305f036e71ada63bc",
|
||||
"title": "Task 15"
|
||||
},
|
||||
{
|
||||
"id": "67a753003a67e1e802515993",
|
||||
"title": "Task 16"
|
||||
},
|
||||
{
|
||||
"id": "67a7541415cd08e8c9a707e9",
|
||||
"title": "Task 17"
|
||||
},
|
||||
{
|
||||
"id": "67a758557a9c6feb3efbf09c",
|
||||
"title": "Task 18"
|
||||
},
|
||||
{
|
||||
"id": "67a7597f958183ec522f4033",
|
||||
"title": "Task 19"
|
||||
},
|
||||
{
|
||||
"id": "67a75a9acd71d2ed6eb9a6fa",
|
||||
"title": "Task 20"
|
||||
},
|
||||
{
|
||||
"id": "67a75c6d5ea4deeee6ffb507",
|
||||
"title": "Task 21"
|
||||
},
|
||||
{
|
||||
"id": "67a75d6b2e42aaefbc7d0d27",
|
||||
"title": "Task 22"
|
||||
},
|
||||
{
|
||||
"id": "67a75e200e190df05e0e8683",
|
||||
"title": "Task 23"
|
||||
},
|
||||
{
|
||||
"id": "67a75f46074d99f1b28459a1",
|
||||
"title": "Task 24"
|
||||
},
|
||||
{
|
||||
"id": "67a760baf99c22f2daba304e",
|
||||
"title": "Task 25"
|
||||
},
|
||||
{
|
||||
"id": "67a8729d524e9b03f6d5b5b4",
|
||||
"title": "Task 26"
|
||||
},
|
||||
{
|
||||
"id": "67a873a23552f704c9a1266e",
|
||||
"title": "Task 27"
|
||||
},
|
||||
{
|
||||
"id": "67a876c1909803066b7b7aa1",
|
||||
"title": "Task 28"
|
||||
},
|
||||
{
|
||||
"id": "67a8ab7d9c41160a85695934",
|
||||
"title": "Task 29"
|
||||
},
|
||||
{
|
||||
"id": "67a8ad121b12900c1baeb882",
|
||||
"title": "Task 30"
|
||||
},
|
||||
{
|
||||
"id": "67a8ae3c3710410d1bf9569c",
|
||||
"title": "Task 31"
|
||||
},
|
||||
{
|
||||
"id": "67a8af564a72170e409ef971",
|
||||
"title": "Task 32"
|
||||
},
|
||||
{
|
||||
"id": "67a8b0ecdf06070f96c7ccdc",
|
||||
"title": "Task 33"
|
||||
},
|
||||
{
|
||||
"id": "67a8b18d14c337106171e769",
|
||||
"title": "Task 34"
|
||||
},
|
||||
{
|
||||
"id": "67a8b767810d4512a77c8988",
|
||||
"title": "Task 35"
|
||||
},
|
||||
{
|
||||
"id": "67a8b900d1f59014ddd66b91",
|
||||
"title": "Task 36"
|
||||
},
|
||||
{
|
||||
"id": "67a98cb3c834fe1b9d887299",
|
||||
"title": "Task 37"
|
||||
},
|
||||
{
|
||||
"id": "67ac5dcf8b2b0424b0769136",
|
||||
"title": "Task 38"
|
||||
},
|
||||
{
|
||||
"id": "67ac5f118ea4752af0866ec5",
|
||||
"title": "Task 39"
|
||||
},
|
||||
{
|
||||
"id": "67ac6046a0c89231c6b99323",
|
||||
"title": "Task 40"
|
||||
},
|
||||
{
|
||||
"id": "67ac640592d43a449d320d6a",
|
||||
"title": "Task 41"
|
||||
},
|
||||
{
|
||||
"id": "67ac663228bb894b6d7541ba",
|
||||
"title": "Task 42"
|
||||
},
|
||||
{
|
||||
"id": "67af35c80225e132c652185b",
|
||||
"title": "Task 43"
|
||||
},
|
||||
{
|
||||
"id": "67af26b82eb35209466f93ae",
|
||||
"title": "Task 44"
|
||||
},
|
||||
{
|
||||
"id": "67af33c72716c82c4d565f0f",
|
||||
"title": "Task 45"
|
||||
},
|
||||
{
|
||||
"id": "67af348a5f1e3b2ed7cff509",
|
||||
"title": "Task 46"
|
||||
},
|
||||
{
|
||||
"id": "67af38efdf48173d0c0636b3",
|
||||
"title": "Task 47"
|
||||
},
|
||||
{
|
||||
"id": "67af429d29bc315537a8fcf8",
|
||||
"title": "Task 48"
|
||||
},
|
||||
{
|
||||
"id": "67af43f7fc63e958e481f14b",
|
||||
"title": "Task 49"
|
||||
},
|
||||
{
|
||||
"id": "67af45555bbf475c945f211f",
|
||||
"title": "Task 50"
|
||||
},
|
||||
{
|
||||
"id": "67af45e075d4cc5e536d055e",
|
||||
"title": "Task 51"
|
||||
},
|
||||
{
|
||||
"id": "67af46a4ec8db360d8f0cc7a",
|
||||
"title": "Task 52"
|
||||
},
|
||||
{
|
||||
"id": "67b1aca09cf3a9ec7234c6fd",
|
||||
"title": "Dialogue 2: Code Review"
|
||||
},
|
||||
{
|
||||
"id": "67b1acde9499a6ed8c01b135",
|
||||
"title": "Task 53"
|
||||
},
|
||||
{
|
||||
"id": "67b1be6f616adc19991819e6",
|
||||
"title": "Task 54"
|
||||
},
|
||||
{
|
||||
"id": "67b1bfd4a309ef1da9b1be60",
|
||||
"title": "Task 55"
|
||||
},
|
||||
{
|
||||
"id": "67b1d55abbc79129344a55a8",
|
||||
"title": "Task 56"
|
||||
},
|
||||
{
|
||||
"id": "67b1d64e7cda992c0296fe7a",
|
||||
"title": "Task 57"
|
||||
},
|
||||
{
|
||||
"id": "67b1d8345211473169794a1d",
|
||||
"title": "Task 58"
|
||||
},
|
||||
{
|
||||
"id": "67b1d8fcf1608833bdc06993",
|
||||
"title": "Task 59"
|
||||
},
|
||||
{
|
||||
"id": "67b1da8af03f0f384749d71f",
|
||||
"title": "Task 60"
|
||||
},
|
||||
{
|
||||
"id": "67b1dbc920478f3bf71f3a86",
|
||||
"title": "Task 61"
|
||||
},
|
||||
{
|
||||
"id": "67b1ddf392f98642178927d4",
|
||||
"title": "Task 62"
|
||||
},
|
||||
{
|
||||
"id": "67b1e06dd84171494a52bfa4",
|
||||
"title": "Task 63"
|
||||
},
|
||||
{
|
||||
"id": "67b1e32a197da650fbdcd7e8",
|
||||
"title": "Task 64"
|
||||
},
|
||||
{
|
||||
"id": "67b1e5d94993e9592af44aaa",
|
||||
"title": "Task 65"
|
||||
},
|
||||
{
|
||||
"id": "67b1e6b6f922765bcd595546",
|
||||
"title": "Task 66"
|
||||
},
|
||||
{
|
||||
"id": "67b1e9d4a9985764d9c2b556",
|
||||
"title": "Task 67"
|
||||
},
|
||||
{
|
||||
"id": "67b1eb878cc95b69e05822b6",
|
||||
"title": "Task 68"
|
||||
},
|
||||
{
|
||||
"id": "67b1ecb619ae816e3d1c77db",
|
||||
"title": "Task 69"
|
||||
},
|
||||
{
|
||||
"id": "67b1edf306ac9d720066d78d",
|
||||
"title": "Task 70"
|
||||
},
|
||||
{
|
||||
"id": "67b2bb2c55db7018a4719406",
|
||||
"title": "Task 71"
|
||||
},
|
||||
{
|
||||
"id": "67b2bca04ca3531ce94de51a",
|
||||
"title": "Task 72"
|
||||
},
|
||||
{
|
||||
"id": "67b2f20700c45e3c6e39a673",
|
||||
"title": "Task 73"
|
||||
},
|
||||
{
|
||||
"id": "67b2f4c60e993343e5f499e6",
|
||||
"title": "Task 74"
|
||||
},
|
||||
{
|
||||
"id": "67b2f6ded80a5349b4cdb55f",
|
||||
"title": "Task 75"
|
||||
},
|
||||
{
|
||||
"id": "67b2f7af2658a24c24d7679e",
|
||||
"title": "Task 76"
|
||||
},
|
||||
{
|
||||
"id": "67b2f8e6655a944fea3b2659",
|
||||
"title": "Task 77"
|
||||
},
|
||||
{
|
||||
"id": "67b2fbd2e2edc358536c2ebf",
|
||||
"title": "Task 78"
|
||||
},
|
||||
{
|
||||
"id": "67b2fcd04c29685b48d0fb67",
|
||||
"title": "Task 79"
|
||||
},
|
||||
{
|
||||
"id": "67b2ffe092d1a263d380dbae",
|
||||
"title": "Task 80"
|
||||
},
|
||||
{
|
||||
"id": "67b3022721bb7c6a5fcb135b",
|
||||
"title": "Task 81"
|
||||
},
|
||||
{
|
||||
"id": "67b328dbb081d0b87e5429ba",
|
||||
"title": "Task 82"
|
||||
},
|
||||
{
|
||||
"id": "67b32f9ba790e9c984503c55",
|
||||
"title": "Task 83"
|
||||
},
|
||||
{
|
||||
"id": "67b3348f2358b3d72ab41995",
|
||||
"title": "Task 84"
|
||||
},
|
||||
{
|
||||
"id": "67b335626b775ed9e802dc9d",
|
||||
"title": "Task 85"
|
||||
},
|
||||
{
|
||||
"id": "67b336b2abc639dda752f06f",
|
||||
"title": "Task 86"
|
||||
},
|
||||
{
|
||||
"id": "67b3387d323f1be321f52e7b",
|
||||
"title": "Task 87"
|
||||
},
|
||||
{
|
||||
"id": "67b447bd1ac6d92bed8e2279",
|
||||
"title": "Dialogue 3: Client Feedback"
|
||||
},
|
||||
{
|
||||
"id": "67b45fed9a8ec037502ba1a7",
|
||||
"title": "Task 88"
|
||||
},
|
||||
{
|
||||
"id": "67b464dbdf4f8b3a378bd74e",
|
||||
"title": "Task 89"
|
||||
},
|
||||
{
|
||||
"id": "67b466d6babe693b6427352b",
|
||||
"title": "Task 90"
|
||||
},
|
||||
{
|
||||
"id": "67b4681b40ac5c3c991e1f51",
|
||||
"title": "Task 91"
|
||||
},
|
||||
{
|
||||
"id": "67b46920c7cf613d9341c0a0",
|
||||
"title": "Task 92"
|
||||
},
|
||||
{
|
||||
"id": "67b46f01f60803410bf3cbf3",
|
||||
"title": "Task 93"
|
||||
},
|
||||
{
|
||||
"id": "67b4701b5498a742481e11a4",
|
||||
"title": "Task 94"
|
||||
},
|
||||
{
|
||||
"id": "67b475c8f434534627c5ccdb",
|
||||
"title": "Task 95"
|
||||
},
|
||||
{
|
||||
"id": "67b475073485eb4552b3f098",
|
||||
"title": "Task 96"
|
||||
},
|
||||
{
|
||||
"id": "67b47fe27ee0174a167d1df3",
|
||||
"title": "Task 97"
|
||||
},
|
||||
{
|
||||
"id": "67b4816b1a89374b977f5104",
|
||||
"title": "Task 98"
|
||||
},
|
||||
{
|
||||
"id": "67b4820e52af174c730e5aa1",
|
||||
"title": "Task 99"
|
||||
},
|
||||
{
|
||||
"id": "67b483d5269d544dc29eb63e",
|
||||
"title": "Task 100"
|
||||
},
|
||||
{
|
||||
"id": "67b484bcc0c1c84ebc873639",
|
||||
"title": "Task 101"
|
||||
},
|
||||
{
|
||||
"id": "67b486c845b16a50534f7adc",
|
||||
"title": "Task 102"
|
||||
},
|
||||
{
|
||||
"id": "67b48778dab13c5146878351",
|
||||
"title": "Task 103"
|
||||
},
|
||||
{
|
||||
"id": "67b488eaaf572e52ace1db68",
|
||||
"title": "Task 104"
|
||||
},
|
||||
{
|
||||
"id": "67b48a6884325454259c2728",
|
||||
"title": "Task 105"
|
||||
},
|
||||
{
|
||||
"id": "67b48b6d08b877551e6ab9a9",
|
||||
"title": "Task 106"
|
||||
},
|
||||
{
|
||||
"id": "67b48cb69012de56a527465c",
|
||||
"title": "Task 107"
|
||||
},
|
||||
{
|
||||
"id": "67b5b02b5759d517626403fd",
|
||||
"title": "Task 108"
|
||||
},
|
||||
{
|
||||
"id": "67b5b0168c10d017204bc455",
|
||||
"title": "Task 109"
|
||||
},
|
||||
{
|
||||
"id": "67b5b3dfdec8df1a5f326bc0",
|
||||
"title": "Task 110"
|
||||
},
|
||||
{
|
||||
"id": "67b5c955211e021fb5902c7d",
|
||||
"title": "Task 111"
|
||||
},
|
||||
{
|
||||
"id": "67b5ccc7d6342721d2822c45",
|
||||
"title": "Task 112"
|
||||
},
|
||||
{
|
||||
"id": "67b5d29123ab4d24c0f1f811",
|
||||
"title": "Task 113"
|
||||
},
|
||||
{
|
||||
"id": "67b5d3b2316c7825d05f9bf5",
|
||||
"title": "Task 114"
|
||||
},
|
||||
{
|
||||
"id": "67b5d4a254618626a2d5fdbc",
|
||||
"title": "Task 115"
|
||||
},
|
||||
{
|
||||
"id": "67b5d5e47e9ed427ca301ed6",
|
||||
"title": "Task 116"
|
||||
},
|
||||
{
|
||||
"id": "67b5d81ffdb8ed2982020232",
|
||||
"title": "Task 117"
|
||||
},
|
||||
{
|
||||
"id": "67b70843a1f069708b3bdd22",
|
||||
"title": "Task 118"
|
||||
},
|
||||
{
|
||||
"id": "67b70aa683211a7200d63056",
|
||||
"title": "Task 119"
|
||||
},
|
||||
{
|
||||
"id": "67b70c48107da6738ff1b365",
|
||||
"title": "Task 120"
|
||||
},
|
||||
{
|
||||
"id": "67b71dba135d38792e63bca3",
|
||||
"title": "Task 121"
|
||||
},
|
||||
{
|
||||
"id": "67b7217d24945c7b4117ccb1",
|
||||
"title": "Task 122"
|
||||
},
|
||||
{
|
||||
"id": "67b722177d22787bc937defc",
|
||||
"title": "Task 123"
|
||||
},
|
||||
{
|
||||
"id": "67b72549a630b47e72e444fa",
|
||||
"title": "Task 124"
|
||||
},
|
||||
{
|
||||
"id": "67b72665e419be7f58ddf646",
|
||||
"title": "Task 125"
|
||||
},
|
||||
{
|
||||
"id": "67b7285a50f200811f380c10",
|
||||
"title": "Task 126"
|
||||
},
|
||||
{
|
||||
"id": "67b7298f4089db82557da0b9",
|
||||
"title": "Task 127"
|
||||
},
|
||||
{
|
||||
"id": "67b72aa97b8a9183736a2c6e",
|
||||
"title": "Task 128"
|
||||
},
|
||||
{
|
||||
"id": "67b72ccdad915684c63fae8b",
|
||||
"title": "Task 129"
|
||||
},
|
||||
{
|
||||
"id": "67b732be2a720d87e1682e90",
|
||||
"title": "Task 130"
|
||||
},
|
||||
{
|
||||
"id": "67b73428c0c6e588c4d8689d",
|
||||
"title": "Task 131"
|
||||
},
|
||||
{
|
||||
"id": "67b73530d8ede28a9875e6b1",
|
||||
"title": "Task 132"
|
||||
},
|
||||
{
|
||||
"id": "67b7359a9a74c38b2252393b",
|
||||
"title": "Task 133"
|
||||
},
|
||||
{
|
||||
"id": "67b736c74795608c6818fed3",
|
||||
"title": "Task 134"
|
||||
}
|
||||
],
|
||||
"helpCategory": "English",
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
id: 6660a04ec4ec815eb81ede7c
|
||||
title: "Dialogue 1: I'm Tom"
|
||||
title: "Dialogue 1: Project Planning"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-1-im-tom
|
||||
dashedName: dialogue-1-project-planning
|
||||
---
|
||||
|
||||
# --description--
|
||||
@@ -11,48 +11,186 @@ Watch the video below to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
Watch the video.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "chaos.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "David",
|
||||
"position": {"x":50,"y":80,"z":8},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "1.1-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 5.7,
|
||||
"finishTimestamp": 6.48
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "David",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "David",
|
||||
"startTime": 1,
|
||||
"finishTime": 0.78,
|
||||
"dialogue": {
|
||||
"text": "I'm Tom.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Tom",
|
||||
"opacity": 0,
|
||||
"startTime": 1.28
|
||||
}
|
||||
]
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.98,
|
||||
"dialogue": {
|
||||
"text": "We need to start planning our new mobile app project. Let's discuss the timeline.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 5.48,
|
||||
"finishTime": 9.3,
|
||||
"dialogue": {
|
||||
"text": "I was thinking we should aim to have the initial prototype ready in four weeks.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 9.5,
|
||||
"finishTime": 10.56,
|
||||
"dialogue": {
|
||||
"text": "Does that sound reasonable?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 11.22,
|
||||
"finishTime": 15.5,
|
||||
"dialogue": {
|
||||
"text": "I think that's doable. We can work on the design sketches this week and then move on to wireframes.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 15.96,
|
||||
"finishTime": 21.52,
|
||||
"dialogue": {
|
||||
"text": "Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the frontend design.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 22.16,
|
||||
"finishTime": 27.68,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. And I can also prepare some user scenarios for testing so we can ensure a smooth user experience.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 27.86,
|
||||
"finishTime": 31.6,
|
||||
"dialogue": {
|
||||
"text": "Good idea. By the way, we need to allocate tasks among the team.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 31.78,
|
||||
"finishTime": 35.82,
|
||||
"dialogue": {
|
||||
"text": "I was thinking that you could lead the UX design and I'll coordinate with the developers.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 75.88,
|
||||
"finishTime": 76.94,
|
||||
"dialogue": {
|
||||
"text": "Does that work for you?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 37.54,
|
||||
"finishTime": 40.72,
|
||||
"dialogue": {
|
||||
"text": "That's a good plan. I'll also keep you updated on the design process",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 40.72,
|
||||
"finishTime": 43.14,
|
||||
"dialogue": {
|
||||
"text": "and we can schedule regular meetings to stay on track.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 43.52,
|
||||
"finishTime": 48.02,
|
||||
"dialogue": {
|
||||
"text": "Perfect. Let's set a weekly meeting to review our progress. Would Friday morning work for you?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 48.5,
|
||||
"finishTime": 53.22,
|
||||
"dialogue": {
|
||||
"text": "Sure. Friday mornings are great. It gives me a chance to review the week's work and plan for the next week.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 53.44,
|
||||
"finishTime": 59.22,
|
||||
"dialogue": {
|
||||
"text": "Great. I'll send out a meeting invite and share the project timeline with everyone. Thanks for your input, Linda.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 59.92,
|
||||
"finishTime": 62.3,
|
||||
"dialogue": {
|
||||
"text": "No problem, Bob. I'm looking forward to working on this project.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 62.8
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 63.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
@@ -0,0 +1,103 @@
|
||||
---
|
||||
id: 677bf6d81eba074172a73a2e
|
||||
title: Task 1
|
||||
challengeType: 22
|
||||
dashedName: task-1
|
||||
---
|
||||
<!-- (Audio) Bob: We need to start planning our new mobile app project. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`We need to start planning our BLANK BLANK BLANK project.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`new`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word describes something that has not existed before or is being introduced for the first time.
|
||||
|
||||
---
|
||||
|
||||
`mobile`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to devices like smartphones or tablets that can be used anywhere.
|
||||
|
||||
---
|
||||
|
||||
`app`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is a short form for `application`, which is software designed for specific tasks.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`New` means something that has not been used, seen, or experienced before. For example:
|
||||
|
||||
`The company launched a new product last week.` - This means the product was recently introduced and didn't exist before.
|
||||
|
||||
`Mobile` refers to something that can move or be used while moving, often associated with technology like phones or tablets. For example:
|
||||
|
||||
`I prefer reading the news on my mobile phone.` - This means you use your phone to access news.
|
||||
|
||||
`App` is a short form of the word `application`, which is a program or software designed for a specific purpose. For example:
|
||||
|
||||
`I use a fitness app to track my workouts.` - This means the app helps monitor exercise routines.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 2.54
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.54,
|
||||
"dialogue": {
|
||||
"text": "We need to start planning our new mobile app project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 4.04
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,105 @@
|
||||
---
|
||||
id: 6780284188c80df6c1483f2f
|
||||
title: Task 2
|
||||
challengeType: 19
|
||||
dashedName: task-2
|
||||
---
|
||||
<!-- (Audio) Bob: We need to start planning our new mobile app project. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What type of project is Bob talking about?
|
||||
|
||||
## --answers--
|
||||
|
||||
A mobile app project
|
||||
|
||||
---
|
||||
|
||||
A website design project
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob doesn't mention anything about a website.
|
||||
|
||||
---
|
||||
|
||||
A desktop application
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob is talking about an app, but is it for desktops? Listen again and think about what kind of app he mentions.
|
||||
|
||||
---
|
||||
|
||||
A marketing project
|
||||
|
||||
### --feedback--
|
||||
|
||||
Does Bob talk about marketing? Listen carefully to what kind of project he wants to plan.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Let's break this down.
|
||||
|
||||
What does Bob say they need to start planning? A `project`.
|
||||
|
||||
What kind of project is it? A `mobile app project`.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 2.54
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.54,
|
||||
"dialogue": {
|
||||
"text": "We need to start planning our new mobile app project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 4.04
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,79 @@
|
||||
---
|
||||
id: 67802a99de4bf605a5397ccd
|
||||
title: Task 3
|
||||
challengeType: 22
|
||||
dashedName: task-3
|
||||
---
|
||||
<!-- (Audio) Bob: Let's discuss the timeline. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Let's discuss the BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`timeline`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word is related to planning or organizing tasks over time.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Timeline` refers to a schedule or plan that organizes tasks or events in a specific order based on time. It helps people stay organized and meet deadlines. For example:
|
||||
|
||||
- `The timeline shows that the event will start at 9 AM and finish at 5 PM.` - This means the timeline provides the specific times when the event will take place.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 2.62,
|
||||
"finishTimestamp": 4.18
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.56,
|
||||
"dialogue": {
|
||||
"text": "Let's discuss the timeline.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 3.06
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,112 @@
|
||||
---
|
||||
id: 67802cab680a85130fd846a0
|
||||
title: Task 4
|
||||
challengeType: 19
|
||||
dashedName: task-4
|
||||
---
|
||||
<!-- (Audio) Bob: We need to start planning our new mobile app project. Let's discuss the timeline. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Why does Bob want to discuss the timeline?
|
||||
|
||||
## --answers--
|
||||
|
||||
To assign tasks to team members.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob doesn't mention assigning tasks.
|
||||
|
||||
---
|
||||
|
||||
To determine the budget.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The timeline isn't about budgeting.
|
||||
|
||||
---
|
||||
|
||||
To prepare the project schedule.
|
||||
|
||||
---
|
||||
|
||||
To review the app's features.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob isn't talking about the app's features.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
To answer this question, think about the purpose of a timeline. It helps to organize tasks, set deadlines, and plan effectively.
|
||||
|
||||
A timeline is used to organize and plan tasks over time. When Bob says, `Let's discuss the timeline`, he is referring to preparing a schedule for the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 3.98
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.54,
|
||||
"dialogue": {
|
||||
"text": "We need to start planning our new mobile app project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 3.72,
|
||||
"finishTime": 4.98,
|
||||
"dialogue": {
|
||||
"text": "Let's discuss the timeline.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.48
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
id: 678030ed8973e82d5b439ff9
|
||||
title: Task 5
|
||||
challengeType: 22
|
||||
dashedName: task-5
|
||||
---
|
||||
<!-- (Audio) Bob: I was thinking we should aim to have the initial prototype ready in four weeks. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I was thinking we should BLANK BLANK BLANK the initial prototype ready in four weeks.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`aim`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to set a goal or target.
|
||||
|
||||
---
|
||||
|
||||
`to`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This preposition connects the verb `aim` with the action that follows.
|
||||
|
||||
---
|
||||
|
||||
`have`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to possess or achieve something.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Aim to have` is a professional expression used to describe setting a goal to achieve something. It shows intention and focus on reaching a target. For example:
|
||||
|
||||
`We aim to have the report completed by Friday.` - This means the goal is to finish the report by Friday.
|
||||
|
||||
Using `aim to have` in conversation shows a clear and polite way of proposing a goal or objective.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 8.3
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I was thinking we should aim to have the initial prototype ready in four weeks.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
id: 678033a501bb6d3e2fc0eb50
|
||||
title: Task 6
|
||||
challengeType: 22
|
||||
dashedName: task-6
|
||||
---
|
||||
<!-- (Audio) Bob: I was thinking we should aim to have the initial prototype ready in four weeks. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I was thinking we should aim to have the BLANK BLANK ready in four weeks.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`initial`
|
||||
|
||||
### --feedback--
|
||||
|
||||
The first or earliest version of something.
|
||||
|
||||
---
|
||||
|
||||
`prototype`
|
||||
|
||||
### --feedback--
|
||||
|
||||
What is an early version of a product called? This version is often created for testing or presenting ideas.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Initial prototype` refers to the first version of a product or project created for testing or presenting ideas. For example:
|
||||
|
||||
`The initial prototype helped the team understand what changes were needed.` - This means the first version was used to identify improvements.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 8.3
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I was thinking we should aim to have the initial prototype ready in four weeks.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,103 @@
|
||||
---
|
||||
id: 67803535dcaa454865db5fd0
|
||||
title: Task 7
|
||||
challengeType: 19
|
||||
dashedName: task-7
|
||||
---
|
||||
<!-- (Audio) Bob: I was thinking we should aim to have the initial prototype ready in four weeks. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Bob suggesting they should do in four weeks?
|
||||
|
||||
## --answers--
|
||||
|
||||
Finalize the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob is not talking about finishing the entire project.
|
||||
|
||||
---
|
||||
|
||||
Launch the product.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob is not suggesting launching the product.
|
||||
|
||||
---
|
||||
|
||||
Review the budget.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob doesn't mention the budget.
|
||||
|
||||
---
|
||||
|
||||
Complete the initial prototype.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
To answer this question, focus on what Bob says they should aim to achieve.
|
||||
|
||||
He mentions the `initial prototype`, which is the first version of the project. The goal is to complete this in four weeks, not finalize the entire project or launch the product.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 8.3
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I was thinking we should aim to have the initial prototype ready in four weeks.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,83 @@
|
||||
---
|
||||
id: 678036b3f7eb4651f6c273c2
|
||||
title: Task 8
|
||||
challengeType: 22
|
||||
dashedName: task-8
|
||||
---
|
||||
<!-- (Audio) Bob: Does that sound reasonable? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Does that sound BLANK?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`reasonable`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means fair, practical, or logical in a given situation.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Reasonable` means fair, practical, or logical based on the context. It is used to ask if something makes sense or is acceptable. For example:
|
||||
|
||||
- `The timeline for completing the project seems reasonable.` - This means the timeline is fair and achievable.
|
||||
|
||||
- `It's reasonable to expect a response within 24 hours.` - This means it is practical and fair to expect a reply within that time.
|
||||
|
||||
Using `reasonable` in conversation shows a polite and professional way **to confirm agreement** or check if a suggestion is acceptable.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 8.4,
|
||||
"finishTimestamp": 9.66
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.26,
|
||||
"dialogue": {
|
||||
"text": "Does that sound reasonable?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 2.76
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,111 @@
|
||||
---
|
||||
id: 679b6fda63e57f01cdd2a45d
|
||||
title: Task 9
|
||||
challengeType: 19
|
||||
dashedName: task-9
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: I was thinking we should aim to have the initial prototype ready in four weeks. Does that sound reasonable? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Bob want to know?
|
||||
|
||||
## --answers--
|
||||
|
||||
If they can finish the prototype in two weeks.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob mentions a different timeline.
|
||||
|
||||
---
|
||||
|
||||
If the team is available to start next week.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not ask about when to start.
|
||||
|
||||
---
|
||||
|
||||
If finishing the prototype in four weeks is a practical goal.
|
||||
|
||||
---
|
||||
|
||||
How much time they need to finish the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob suggests a timeframe but does not ask how much time is needed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Bob wants to confirm if `four weeks` is a `reasonable` amount of time to complete the `initial prototype`. He is not asking for a different estimate or a start date.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 9.56
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I was thinking we should aim to have the initial prototype ready in four weeks.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 5.02,
|
||||
"finishTime": 6.08,
|
||||
"dialogue": {
|
||||
"text": "Does that sound reasonable?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 6.58
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: 679b72572a03cc037def37c3
|
||||
title: Task 11
|
||||
challengeType: 22
|
||||
dashedName: task-11
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: I think that's doable. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I think that's BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`doable`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means something is possible to achieve.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Doable` means something is possible or achievable. It is often used in informal conversations to express that a task or goal can be completed. For example:
|
||||
|
||||
- `Finishing this project by Friday is doable.` – This means completing the project by Friday is possible.
|
||||
|
||||
- `Is it doable within our budget?` – This asks if something can be achieved with the available money.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 10.22,
|
||||
"finishTimestamp": 11.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.0,
|
||||
"dialogue": {
|
||||
"text": "I think that's doable.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 2.5
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 679b73bd4f95b4048fe6f9b9
|
||||
title: Task 12
|
||||
challengeType: 22
|
||||
dashedName: task-12
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: We can work on the design sketches this week and then move on to wireframes. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`We can work on the design BLANK this week and then move on to BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`sketches`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word in the plural form refers to rough drawings or drafts.
|
||||
|
||||
---
|
||||
|
||||
`wireframes`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word in the plural form refers to basic layouts or structures of a design.
|
||||
|
||||
# --explanation--
|
||||
|
||||
A `sketch` is a rough drawing used to plan or visualize an idea. For example:
|
||||
|
||||
`She made a quick sketch of the website layout before designing it digitally.` – This means she created a simple drawing before starting the actual design.
|
||||
|
||||
A `wireframe` is a simple outline or blueprint of a digital design, showing structure without details. For example:
|
||||
|
||||
`The team created wireframes to plan the website's navigation before adding colors and images.` – This means they first designed a basic structure before working on the visual details.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 11.36,
|
||||
"finishTimestamp": 14.5
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.14,
|
||||
"dialogue": {
|
||||
"text": "We can work on the design sketches this week and then move on to wireframes.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 4.64
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,113 @@
|
||||
---
|
||||
id: 679b74ee20b7400598e672ce
|
||||
title: Task 13
|
||||
challengeType: 19
|
||||
dashedName: task-13
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: I think that's doable. We can work on the design sketches this week and then move on to wireframes. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Linda say about Bob's timeline?
|
||||
|
||||
## --answers--
|
||||
|
||||
She says the timeline is too short.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not say the timeline is too short.
|
||||
|
||||
---
|
||||
|
||||
She agrees with the timeline and suggests a plan.
|
||||
|
||||
---
|
||||
|
||||
She asks for more time to prepare.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not ask for extra time.
|
||||
|
||||
---
|
||||
|
||||
She says they should start with wireframes.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda suggests starting with design sketches first.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
Linda supports Bob's timeline by saying `I think that's doable`, which means she believes it is achievable.
|
||||
|
||||
She then proposes a plan: starting with `design sketches` and moving on to `wireframes.` This shows she agrees and has a clear next step in mind.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 10.22,
|
||||
"finishTimestamp": 14.5
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 1.8,
|
||||
"dialogue": {
|
||||
"text": "I think that's doable.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 2.14,
|
||||
"finishTime": 5.28,
|
||||
"dialogue": {
|
||||
"text": "We can work on the design sketches this week and then move on to wireframes.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 5.78
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
id: 679b7597814cfe0657acb4f5
|
||||
title: Task 10
|
||||
challengeType: 19
|
||||
dashedName: task-10
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: I was thinking we should aim to have the initial prototype ready in four weeks. Does that sound reasonable? -->
|
||||
|
||||
<!-- SPEAKING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
How can Linda say that she agrees with the proposed plan?
|
||||
|
||||
## --answers--
|
||||
|
||||
`I think that's doable.`
|
||||
|
||||
---
|
||||
|
||||
`That won't work for me.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This expresses disagreement, not agreement.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
`I think that's doable` means the plan is achievable or realistic. It is a polite and natural way to express agreement when discussing project timelines or tasks.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.48,
|
||||
"finishTimestamp": 9.56
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.82,
|
||||
"dialogue": {
|
||||
"text": "I was thinking we should aim to have the initial prototype ready in four weeks.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 5.02,
|
||||
"finishTime": 6.08,
|
||||
"dialogue": {
|
||||
"text": "Does that sound reasonable?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 6.58
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: 67a74fd46f19afe4d0aff00f
|
||||
title: Task 14
|
||||
challengeType: 22
|
||||
dashedName: task-14
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Exactly`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word confirms agreement and emphasizes a point. The first letter is capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Exactly` is used to confirm a statement or express strong agreement. It reinforces an idea or supports what someone else has said. For example:
|
||||
|
||||
- Person 1: `The client wants a more modern UI.`
|
||||
|
||||
- Person 2: `Exactly. That's why we're redesigning the dashboard with a cleaner layout.` - Here, `exactly` is used to strongly agree with the statement and emphasize the reason for the UI redesign.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 14.66,
|
||||
"finishTimestamp": 20.52
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.86,
|
||||
"dialogue": {
|
||||
"text": "Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 7.36
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67a751e305f036e71ada63bc
|
||||
title: Task 15
|
||||
challengeType: 19
|
||||
dashedName: task-15
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Bob's response suggest about his opinion of Linda's idea?
|
||||
|
||||
## --answers--
|
||||
|
||||
He is unsure and wants more details.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not ask for clarification or more details.
|
||||
|
||||
---
|
||||
|
||||
He strongly agrees with her.
|
||||
|
||||
---
|
||||
|
||||
He disagrees and suggests a different approach.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not express disagreement or propose an alternative idea.
|
||||
|
||||
---
|
||||
|
||||
He thinks it's possible but needs adjustments.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not mention any adjustments or modifications.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that show Bob's opinion.
|
||||
|
||||
`Exactly` – This word indicates strong agreement with what was said.
|
||||
|
||||
`we can start collaborating` – This suggests he is ready to move forward with the idea rather than questioning or changing it.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 14.66,
|
||||
"finishTimestamp": 20.52
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.86,
|
||||
"dialogue": {
|
||||
"text": "Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 7.36
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,104 @@
|
||||
---
|
||||
id: 67a753003a67e1e802515993
|
||||
title: Task 16
|
||||
challengeType: 22
|
||||
dashedName: task-16
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Exactly. Once we have the wireframes, we can start BLANK with the developers to BLANK the BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`collaborating`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means working together with others on a project. It ends with `-ing`.
|
||||
|
||||
---
|
||||
|
||||
`implement`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb means to put a plan or idea into action.
|
||||
|
||||
---
|
||||
|
||||
`front-end design`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase refers to the visual and interactive part of a website or application. The first word is a compound word. Remember to use `-`.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Collaborating` means working with others to achieve a common goal. It is often used in teamwork or project-based work. For example:
|
||||
|
||||
`The designers and developers are collaborating to improve the user experience.` – This means they are working together to make the interface more user-friendly.
|
||||
|
||||
`Implement` means to put a plan or decision into action. For example:
|
||||
|
||||
`The team will implement a new authentication system next month.` – This means they will set up and start using a new way for users to log in.
|
||||
|
||||
`Front-end design` refers to the part of a website or app that users interact with directly. For example:
|
||||
|
||||
`The front-end design of the app was updated to make it more modern and intuitive.` – This means the visual and interactive elements were changed to improve the user experience.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 14.66,
|
||||
"finishTimestamp": 20.52
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.86,
|
||||
"dialogue": {
|
||||
"text": "Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 7.36
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,108 @@
|
||||
---
|
||||
id: 67a7541415cd08e8c9a707e9
|
||||
title: Task 17
|
||||
challengeType: 19
|
||||
dashedName: task-17
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is the next step after the wireframes are ready?
|
||||
|
||||
## --answers--
|
||||
|
||||
Start testing the back-end functionality.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not mention back-end testing in his response.
|
||||
|
||||
---
|
||||
|
||||
Finalize the wireframes with the design team.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob talks about what happens after the wireframes are ready, not about making changes to them.
|
||||
|
||||
---
|
||||
|
||||
Give the wireframes to the client for approval.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not mention a client or approval process.
|
||||
|
||||
---
|
||||
|
||||
Work with developers to build the front end.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that indicate the next step.
|
||||
|
||||
`Once we have the wireframes` – This signals that Bob is talking about what happens after they are ready.
|
||||
|
||||
`Start collaborating with the developers` – This shows that the next step involves working with developers.
|
||||
|
||||
`Implement the front-end design` – This confirms that the focus is on building the front end.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 14.66,
|
||||
"finishTimestamp": 20.52
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.86,
|
||||
"dialogue": {
|
||||
"text": "Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 7.36
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: 67a758557a9c6feb3efbf09c
|
||||
title: Task 18
|
||||
challengeType: 22
|
||||
dashedName: task-18
|
||||
---
|
||||
|
||||
<!-- (audio) Linda: Absolutely. And I can also prepare some user scenarios for testing, so we can ensure a smooth user experience. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK. And I can also prepare some user scenarios for testing, so we can ensure a smooth user experience.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Absolutely`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word is used to strongly agree with something. The first letter is capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Absolutely` is used to express strong agreement or confirmation. For example:
|
||||
|
||||
- Person 1: `We should prioritize mobile responsiveness.`
|
||||
|
||||
- Person 2: `Absolutely! Most users access our site from their phones.` - This person completely agrees that mobile responsiveness is important.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.86,
|
||||
"finishTimestamp": 26.68
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.82,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. And I can also prepare some user scenarios for testing so we can ensure a smooth user experience.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,108 @@
|
||||
---
|
||||
id: 67a7597f958183ec522f4033
|
||||
title: Task 19
|
||||
challengeType: 19
|
||||
dashedName: task-19
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: Absolutely. And I can also prepare some user scenarios for testing, so we can ensure a smooth user experience. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
How does Linda feel about the idea being discussed?
|
||||
|
||||
## --answers--
|
||||
|
||||
She is unsure and needs more details.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not express doubt or ask for more information.
|
||||
|
||||
---
|
||||
|
||||
She disagrees and suggests a different approach.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not disagree or propose an alternative plan.
|
||||
|
||||
---
|
||||
|
||||
She completely agrees with it.
|
||||
|
||||
---
|
||||
|
||||
She thinks it might work but needs adjustments.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not mention any changes or modifications.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that indicate Linda's attitude toward the idea.
|
||||
|
||||
`Absolutely` – This word expresses strong agreement and confidence.
|
||||
|
||||
`I can also` – This suggests she is not just agreeing but actively contributing by adding her own idea.
|
||||
|
||||
`Prepare some user scenarios for testing` – This shows she is thinking ahead and helping move the idea forward.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.86,
|
||||
"finishTimestamp": 26.68
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.82,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. And I can also prepare some user scenarios for testing so we can ensure a smooth user experience.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,80 @@
|
||||
---
|
||||
id: 67a75a9acd71d2ed6eb9a6fa
|
||||
title: Task 20
|
||||
challengeType: 22
|
||||
dashedName: task-20
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: Absolutely. And I can also prepare some user scenarios for testing, so we can ensure a smooth user experience. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Absolutely. And I can also prepare some BLANK for testing, so we can ensure a smooth user experience.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`user scenarios`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase refers to different situations that represent how a person might interact with a product.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`User scenarios` refers to different situations that describe how users interact with a product to achieve a goal. It helps teams test and improve the user experience. For example:
|
||||
|
||||
`We created user scenarios to see how customers navigate the checkout process.` – This means the team simulated different ways users complete a purchase to identify any issues.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.86,
|
||||
"finishTimestamp": 26.68
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.82,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. And I can also prepare some user scenarios for testing so we can ensure a smooth user experience.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,108 @@
|
||||
---
|
||||
id: 67a75c6d5ea4deeee6ffb507
|
||||
title: Task 21
|
||||
challengeType: 19
|
||||
dashedName: task-21
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: Absolutely. And I can also prepare some user scenarios for testing, so we can ensure a smooth user experience. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Linda offer to do?
|
||||
|
||||
## --answers--
|
||||
|
||||
Prepare user scenarios for testing.
|
||||
|
||||
---
|
||||
|
||||
Skip the testing phase.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not suggest skipping testing; she is actively contributing to it.
|
||||
|
||||
---
|
||||
|
||||
Ask someone else to handle user testing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not delegate the task to someone else.
|
||||
|
||||
---
|
||||
|
||||
Redesign the user interface from scratch.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not talk about redesigning the interface.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that indicate what Linda is offering to do.
|
||||
|
||||
`I can also` – This shows she is volunteering to contribute.
|
||||
|
||||
`Prepare some user scenarios for testing` – This clearly states the task she is taking responsibility for.
|
||||
|
||||
`Ensure a smooth user experience` – This explains why testing is important and reinforces her commitment to the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.86,
|
||||
"finishTimestamp": 26.68
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.82,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. And I can also prepare some user scenarios for testing so we can ensure a smooth user experience.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67a75d6b2e42aaefbc7d0d27
|
||||
title: Task 22
|
||||
challengeType: 19
|
||||
dashedName: task-22
|
||||
---
|
||||
|
||||
<!-- SPEAKING -->
|
||||
|
||||
<!-- (Audio) Linda: And I can also prepare some user scenarios for testing, so we can ensure a smooth user experience. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Bob agrees with Linda, what should he say?
|
||||
|
||||
## --answers--
|
||||
|
||||
`That's not necessary right now.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This response suggests disagreement, not agreement.
|
||||
|
||||
---
|
||||
|
||||
`Good idea.`
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
If Bob agrees with Linda, he would respond positively. A phrase like `good idea` shows approval of her suggestion.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 20.86,
|
||||
"finishTimestamp": 26.68
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.82,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. And I can also prepare some user scenarios for testing so we can ensure a smooth user experience.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.32
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: 67a75e200e190df05e0e8683
|
||||
title: Task 23
|
||||
challengeType: 22
|
||||
dashedName: task-23
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Good idea. By the way, we need to allocate tasks among the team. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK. By the way, we need to allocate tasks among the team.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Good idea`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase is used to show agreement with a suggestion. The first letter of the first word is capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Good idea` is used to express agreement or approval of a suggestion. It is commonly used in discussions to acknowledge a helpful proposal. For example:
|
||||
|
||||
- Person 1: `Let's set up a shared document for tracking progress.`
|
||||
|
||||
- Person 2: `Good idea. That will help everyone stay updated.` - This person agrees that having a shared document will improve communication.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 26.76,
|
||||
"finishTimestamp": 30.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Good idea. By the way, we need to allocate tasks among the team.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,80 @@
|
||||
---
|
||||
id: 67a75f46074d99f1b28459a1
|
||||
title: Task 24
|
||||
challengeType: 22
|
||||
dashedName: task-24
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Good idea. By the way, we need to allocate tasks among the team. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Good idea. BLANK, we need to allocate tasks among the team.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`By the way`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This three-word phrase is used to introduce a new but related topic. The first letter of the first word is capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`By the way` is used to smoothly introduce a new but related topic in a conversation. It helps transition from one point to another. For example:
|
||||
|
||||
`The design looks great. By the way, have we scheduled the client meeting?` – This means the speaker acknowledges the design and then shifts to another important topic.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 26.76,
|
||||
"finishTimestamp": 30.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Good idea. By the way, we need to allocate tasks among the team.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
id: 67a760baf99c22f2daba304e
|
||||
title: Task 25
|
||||
challengeType: 19
|
||||
dashedName: task-25
|
||||
---
|
||||
|
||||
# --instructions--
|
||||
|
||||
This task doesn't have audio. Read the question below and select the correct answer.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Which sentence uses `by the way` correctly?
|
||||
|
||||
## --answers--
|
||||
|
||||
`We are focusing on the front end, by the way, the back end will be handled separately.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
`By the way` should be used to introduce a new, related topic.
|
||||
|
||||
---
|
||||
|
||||
`I will finish the report, by the way, before the deadline.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This usage feels awkward. `By the way` should introduce a different or unrelated topic, not just add more details.
|
||||
|
||||
---
|
||||
|
||||
`We need to finish the design by Friday. By the way, have you updated the documentation?`
|
||||
|
||||
---
|
||||
|
||||
`The meeting is at 10 AM, by the way, I'll send the agenda shortly.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
`By the way` should introduce a new topic, but here, it's used to add additional details in a way that feels out of place.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
`By the way` is used to introduce a new topic that is somewhat related but not directly connected to the previous statement. For example:
|
||||
|
||||
`We need to finish the design by Friday. By the way, have you updated the documentation?` – The second sentence shifts to a different but relevant topic in the conversation.
|
||||
|
||||
Incorrect uses often try to connect ideas too closely or add extra details instead of introducing a new topic. The correct answer shows how `by the way` smoothly transitions to a different point in a natural way.
|
||||
@@ -0,0 +1,80 @@
|
||||
---
|
||||
id: 67a8729d524e9b03f6d5b5b4
|
||||
title: Task 26
|
||||
challengeType: 22
|
||||
dashedName: task-26
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Good idea. By the way, we need to allocate tasks among the team. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Good idea. By the way, we need to BLANK tasks among the team.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`allocate`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to distribute or assign resources or responsibilities.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Allocate` means to distribute or assign something, such as tasks, time, or resources, among a group. For example:
|
||||
|
||||
`The manager will allocate tasks based on each team member's strengths.` – This means the manager will assign responsibilities in a way that best fits each person's skills.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 26.76,
|
||||
"finishTimestamp": 30.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Good idea. By the way, we need to allocate tasks among the team.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67a873a23552f704c9a1266e
|
||||
title: Task 27
|
||||
challengeType: 19
|
||||
dashedName: task-27
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Good idea. By the way, we need to allocate tasks among the team. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Bob's main idea?
|
||||
|
||||
## --answers--
|
||||
|
||||
Making sure he completes all the tasks himself.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob doesn't talk about handling everything alone.
|
||||
|
||||
---
|
||||
|
||||
Delaying task assignments for later.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob says they `need to allocate tasks`, which suggests urgency, not postponement.
|
||||
|
||||
---
|
||||
|
||||
Ensuring tasks are divided among the team.
|
||||
|
||||
---
|
||||
|
||||
Checking which tasks have already been finished.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob does not mention reviewing completed work.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that show Bob's main idea.
|
||||
|
||||
`By the way` – This signals a shift to a new but relevant topic.
|
||||
|
||||
`We need to allocate tasks` – This clearly states that distributing work among the team is necessary.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 26.76,
|
||||
"finishTimestamp": 30.7
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Good idea. By the way, we need to allocate tasks among the team.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67a876c1909803066b7b7aa1
|
||||
title: Task 28
|
||||
challengeType: 22
|
||||
dashedName: task-28
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: I was thinking that you could lead the UX design, and I'll coordinate with the developers. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I was thinking that you could BLANK the BLANK design, and I'll coordinate with the developers.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`lead`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to take charge or be responsible for something.
|
||||
|
||||
---
|
||||
|
||||
`UX`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This abbreviation stands for `user experience`, which focuses on how a product feels and functions for users. Both letters are capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`To lead` means to take charge or be responsible for a task or project. For example:
|
||||
|
||||
`She will lead the development team on the new app.` – This means she will be in charge of managing and guiding the team.
|
||||
|
||||
The abbreviation `UX` stands for `user experience`, which refers to how a user interacts with a product. For example:
|
||||
|
||||
`The UX of this website is very intuitive.` – This means the website is easy to navigate and provides a good experience for users.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 30.78,
|
||||
"finishTimestamp": 34.82
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.04,
|
||||
"dialogue": {
|
||||
"text": "I was thinking that you could lead the UX design and I'll coordinate with the developers.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.54
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: 67a8ab7d9c41160a85695934
|
||||
title: Task 29
|
||||
challengeType: 22
|
||||
dashedName: task-29
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: I was thinking that you could lead the UX design, and I'll coordinate with the developers. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I was thinking that you could lead the UX design, and I'll BLANK BLANK the developers.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`coordinate`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to organize or arrange tasks or people to work together.
|
||||
|
||||
---
|
||||
|
||||
`with`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This preposition is used to show the relationship or action between two people or things.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Coordinate` means to organize and make sure that tasks, people, or things work well together.
|
||||
|
||||
`Coordinate with` is used when talking about working together with someone or a group. For example:
|
||||
|
||||
`I will coordinate with the marketing team to plan the product launch.` – This means working together with the marketing team to plan and organize the launch.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 30.78,
|
||||
"finishTimestamp": 34.82
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.04,
|
||||
"dialogue": {
|
||||
"text": "I was thinking that you could lead the UX design and I'll coordinate with the developers.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.54
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67a8ad121b12900c1baeb882
|
||||
title: Task 30
|
||||
challengeType: 19
|
||||
dashedName: task-30
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: I was thinking that you could lead the UX design, and I'll coordinate with the developers. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Bob suggest?
|
||||
|
||||
## --answers--
|
||||
|
||||
He wants to take charge of the entire project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob doesn't suggest taking over the entire project himself.
|
||||
|
||||
---
|
||||
|
||||
He plans to work on the UX design himself.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob says Linda will lead the UX design.
|
||||
|
||||
---
|
||||
|
||||
He will handle the coordination of all tasks.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob doesn't mention handling all tasks.
|
||||
|
||||
---
|
||||
|
||||
He proposes allocating responsibilities between himself and Linda.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that show how Bob wants to divide responsibilities.
|
||||
|
||||
`You could lead the UX design` – This shows that Bob is assigning this task to Linda.
|
||||
|
||||
`I'll coordinate with the developers` – This clarifies Bob's role in the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 30.78,
|
||||
"finishTimestamp": 34.82
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.04,
|
||||
"dialogue": {
|
||||
"text": "I was thinking that you could lead the UX design and I'll coordinate with the developers.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.54
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67a8ae3c3710410d1bf9569c
|
||||
title: Task 31
|
||||
challengeType: 19
|
||||
dashedName: task-31
|
||||
---
|
||||
|
||||
<!-- SPEAKING -->
|
||||
|
||||
<!-- (Audio) Bob: Does that work for you? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What would be a good response if Linda agrees with Bob?
|
||||
|
||||
## --answers--
|
||||
|
||||
`I'm not sure about that.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This answer doesn't show agreement with Bob. It suggests uncertainty.
|
||||
|
||||
---
|
||||
|
||||
`That's a good plan.`
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
`That's a good plan` shows agreement with Bob's suggestion. It confirms that the idea works for Linda.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_19-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 74.68,
|
||||
"finishTimestamp": 75.94
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.26,
|
||||
"dialogue": {
|
||||
"text": "Does that work for you?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 2.76
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,113 @@
|
||||
---
|
||||
id: 67a8af564a72170e409ef971
|
||||
title: Task 32
|
||||
challengeType: 22
|
||||
dashedName: task-32
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: That's a good plan. I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK BLANK BLANK BLANK. I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`That's`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is a contraction of `that is`. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`a`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is an indefinite article used before singular nouns.
|
||||
|
||||
---
|
||||
|
||||
`good`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word describes something that is beneficial or favorable.
|
||||
|
||||
---
|
||||
|
||||
`plan`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is a set of actions or steps designed to achieve a specific goal.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`That's a good plan` is used to express approval or agreement with a proposed idea or course of action. For example:
|
||||
|
||||
`I agree with you that we should improve the website's navigation. That's a good plan.` – This means the idea of improving navigation is a positive and acceptable suggestion.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 36.54,
|
||||
"finishTimestamp": 42.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 1.74,
|
||||
"dialogue": {
|
||||
"text": "That's a good plan.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1.9,
|
||||
"finishTime": 6.6,
|
||||
"dialogue": {
|
||||
"text": "I'll also keep you updated on the design process and we can schedule regular meetings to stay on track.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.1
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,96 @@
|
||||
---
|
||||
id: 67a8b0ecdf06070f96c7ccdc
|
||||
title: Task 33
|
||||
challengeType: 22
|
||||
dashedName: task-33
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I'll also BLANK BLANK BLANK on the design progress, and we can schedule regular meetings to stay on track.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`keep`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to continue or maintain something.
|
||||
|
||||
---
|
||||
|
||||
`you`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is a pronoun referring to the person being addressed.
|
||||
|
||||
---
|
||||
|
||||
`updated`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to provide the latest information or news.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Keep you updated` means to continue providing the latest information or status about something. For example:
|
||||
|
||||
`I'll keep you updated on the project status.` – This means you will regularly inform them about the progress or changes in the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 37.44,
|
||||
"finishTimestamp": 42.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.7,
|
||||
"dialogue": {
|
||||
"text": "I'll also keep you updated on the design process and we can schedule regular meetings to stay on track.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 6.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67a8b18d14c337106171e769
|
||||
title: Task 34
|
||||
challengeType: 22
|
||||
dashedName: task-34
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I'll also keep you updated on the design progress, and we can BLANK BLANK meetings to stay on track.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`schedule`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to arrange or plan something for a particular time.
|
||||
|
||||
---
|
||||
|
||||
`regular`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means happening at fixed intervals or in a consistent pattern.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Schedule` means to plan or arrange something for a specific time. For example:
|
||||
|
||||
`We need to schedule a meeting for next week.` – This means you need to arrange a meeting at a specific time next week.
|
||||
|
||||
`Regular` refers to something that happens at consistent, predictable intervals. For example:
|
||||
|
||||
`We have regular check-ins every Monday morning.` – This means the check-ins happen consistently every Monday morning.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 37.44,
|
||||
"finishTimestamp": 42.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.7,
|
||||
"dialogue": {
|
||||
"text": "I'll also keep you updated on the design process and we can schedule regular meetings to stay on track.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 6.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,100 @@
|
||||
---
|
||||
id: 67a8b767810d4512a77c8988
|
||||
title: Task 35
|
||||
challengeType: 22
|
||||
dashedName: task-35
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I'll also keep you updated on the design progress, and we can schedule regular meetings to BLANK BLANK BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`stay`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to remain or continue in a particular state or condition.
|
||||
|
||||
---
|
||||
|
||||
`on`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word shows the position or direction related to a surface or a topic.
|
||||
|
||||
---
|
||||
|
||||
`track`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to the path, plan, or progress that is being followed.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Track` refers to a specific course, direction, or plan that is being followed. For example:
|
||||
|
||||
`We need to keep the project on track.` – This means ensuring that the project follows the planned course and is progressing as expected.
|
||||
|
||||
`Stay on track` means to continue focusing on a goal or plan and not let distractions or obstacles interfere. For example:
|
||||
|
||||
`We need to stay on track to finish the design by the end of the week.` – This means the team needs to keep their focus and follow the plan to complete the design on time.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 37.44,
|
||||
"finishTimestamp": 42.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.7,
|
||||
"dialogue": {
|
||||
"text": "I'll also keep you updated on the design process and we can schedule regular meetings to stay on track.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 6.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,115 @@
|
||||
---
|
||||
id: 67a8b900d1f59014ddd66b91
|
||||
title: Task 36
|
||||
challengeType: 19
|
||||
dashedName: task-36
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: That's a good plan. I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What will Linda do to ensure the design stays on track?
|
||||
|
||||
## --answers--
|
||||
|
||||
She will make sure the team works faster.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is not mentioned in the audio.
|
||||
|
||||
---
|
||||
|
||||
She will keep the team updated and schedule regular meetings.
|
||||
|
||||
---
|
||||
|
||||
She will work on the design herself and ensure it stays on track.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda does not mention working alone.
|
||||
|
||||
---
|
||||
|
||||
She will reduce the number of meetings to save time.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is the opposite of what Linda suggests.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that show how Linda plans to keep the design on track.
|
||||
|
||||
`Keep you updated` – This means she will regularly share progress updates.
|
||||
|
||||
`Schedule regular meetings` – This shows she wants to set up meetings to ensure the team stays aligned.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 36.54,
|
||||
"finishTimestamp": 42.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 1.74,
|
||||
"dialogue": {
|
||||
"text": "That's a good plan.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1.9,
|
||||
"finishTime": 6.6,
|
||||
"dialogue": {
|
||||
"text": "I'll also keep you updated on the design process and we can schedule regular meetings to stay on track.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 7.1
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,113 @@
|
||||
---
|
||||
id: 67a98cb3c834fe1b9d887299
|
||||
title: Task 37
|
||||
challengeType: 22
|
||||
dashedName: task-37
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Perfect. Let's set a weekly meeting to review our progress. Would Friday morning work for you? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK. Let's set a BLANK to review our progress. Would BLANK work for you?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Perfect`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word is used to express agreement or approval, often when something is seen as ideal or satisfactory. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`weekly meeting`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase refers to a meeting that takes place once every week to discuss ongoing progress or tasks.
|
||||
|
||||
---
|
||||
|
||||
`Friday morning`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These two words refer to the day of the week and time period when the meeting might happen, indicating a precise time to schedule something. The first letter of the first word is capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Perfect` is often used to express agreement or enthusiasm about something. For example:
|
||||
|
||||
`That's a perfect idea.` – This means the idea is great or ideal.
|
||||
|
||||
`Weekly meeting` refers to a meeting that occurs regularly every week, typically for status updates or progress reviews. For example:
|
||||
|
||||
`We have a weekly meeting every Monday morning.` – This means a meeting is scheduled every Monday to discuss updates.
|
||||
|
||||
`Friday morning` specifies a time frame, in this case, the morning of a specific day of the week (Friday). For example:
|
||||
|
||||
`Our team will meet on Friday morning to discuss the project.` – This means the meeting is set for Friday, in the morning.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 42.32,
|
||||
"finishTimestamp": 47.02
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.08,
|
||||
"dialogue": {
|
||||
"text": "Perfect. Let's set a weekly meeting to review our progress.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 4.38,
|
||||
"finishTime": 5.7,
|
||||
"dialogue": {
|
||||
"text": "Would Friday morning work for you?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 6.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,117 @@
|
||||
---
|
||||
id: 67ac5dcf8b2b0424b0769136
|
||||
title: Task 38
|
||||
challengeType: 19
|
||||
dashedName: task-38
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Perfect. Let's set a weekly meeting to review our progress. Would Friday morning work for you? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Bob proposing?
|
||||
|
||||
## --answers--
|
||||
|
||||
He is suggesting a weekly meeting on Friday morning to review progress.
|
||||
|
||||
---
|
||||
|
||||
He is suggesting a one-time meeting to review progress.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The audio indicates Bob is suggesting a recurring weekly meeting, not a one-time event.
|
||||
|
||||
---
|
||||
|
||||
He is asking for feedback on the progress of the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob is not giving feedback on the project's progress.
|
||||
|
||||
---
|
||||
|
||||
He is asking if Friday morning is a good time for the team to work.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Although Bob asks if Friday morning works, he is actually proposing the meeting for that time.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that indicate Bob's proposal.
|
||||
|
||||
`Let's set a weekly meeting` – This shows he is suggesting a recurring meeting, not a one-time event.
|
||||
|
||||
`To review our progress` – This clarifies the purpose of the meeting.
|
||||
|
||||
`Would Friday morning work for you?` – This confirms he is proposing Friday morning as the meeting time.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 42.32,
|
||||
"finishTimestamp": 47.02
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.08,
|
||||
"dialogue": {
|
||||
"text": "Perfect. Let's set a weekly meeting to review our progress.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 4.38,
|
||||
"finishTime": 5.7,
|
||||
"dialogue": {
|
||||
"text": "Would Friday morning work for you?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 6.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
id: 67ac5f118ea4752af0866ec5
|
||||
title: Task 39
|
||||
challengeType: 22
|
||||
dashedName: task-39
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: Sure, Friday mornings are great. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK, Friday mornings are great.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Sure`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is often used to express agreement or affirmation. It's a casual way of saying "yes" or confirming something. The first letter is capitalized.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Sure` is commonly used to express agreement or to confirm something positively. For example:
|
||||
|
||||
`Sure, I can help with that.` – This means you agree to help.
|
||||
|
||||
In this audio, Linda agrees that Friday mornings work well for a meeting.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 47.3,
|
||||
"finishTimestamp": 48.86
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.56,
|
||||
"dialogue": {
|
||||
"text": "Sure. Friday mornings are great.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 3.06
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,116 @@
|
||||
---
|
||||
id: 67ac6046a0c89231c6b99323
|
||||
title: Task 40
|
||||
challengeType: 19
|
||||
dashedName: task-40
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: Sure, Friday mornings are great. It gives me a chance to review the week's work and plan for the next week. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Why does Linda think Friday mornings are ideal for meetings?
|
||||
|
||||
## --answers--
|
||||
|
||||
It gives her time to focus on her reports and prepare for the following week.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda doesn't mention reports.
|
||||
|
||||
---
|
||||
|
||||
It helps her stay on top of the project's progress.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda doesn't mention staying updated on the project.
|
||||
|
||||
---
|
||||
|
||||
It allows her to plan and prepare her work for the upcoming week.
|
||||
|
||||
---
|
||||
|
||||
She has no other time available for meetings during the week.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda doesn't mention that Friday mornings are her only available time.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that explain why Linda prefers Friday mornings.
|
||||
|
||||
`Review the week's work` – This shows she uses the time to reflect on what has been completed.
|
||||
|
||||
`Plan for the next week` – This indicates she sees the meeting as a way to prepare for upcoming tasks.
|
||||
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 47.3,
|
||||
"finishTimestamp": 52.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.56,
|
||||
"dialogue": {
|
||||
"text": "Sure. Friday mornings are great.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 2.98,
|
||||
"finishTime": 5.92,
|
||||
"dialogue": {
|
||||
"text": "It gives me a chance to review the week's work and plan for the next week.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 6.42
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67ac640592d43a449d320d6a
|
||||
title: Task 41
|
||||
challengeType: 22
|
||||
dashedName: task-41
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Great! I'll send out a meeting invite and share the project timeline with everyone. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK! I'll send out a meeting invite and share the project BLANK with everyone.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Great`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is often used as an informal way to show agreement or approval. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`timeline`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is a schedule or plan that outlines the key events and deadlines of a project. It helps everyone understand the project's deadlines and progress.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Great` is often used to express agreement, showing that the speaker is satisfied with a suggestion or plan. For example:
|
||||
|
||||
`Great, let's do that!` – This means the speaker agrees with the suggestion and is happy to proceed with it.
|
||||
|
||||
`Timeline` refers to a schedule or a plan that organizes the events of a project over time. For example:
|
||||
|
||||
`We need to create a timeline to finish the project on time.` – This means creating a schedule to organize and complete the tasks within a set period.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 52.44,
|
||||
"finishTimestamp": 56.36
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.92,
|
||||
"dialogue": {
|
||||
"text": "Great. I'll send out a meeting invite and share the project timeline with everyone.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.42
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,107 @@
|
||||
---
|
||||
id: 67ac663228bb894b6d7541ba
|
||||
title: Task 42
|
||||
challengeType: 19
|
||||
dashedName: task-42
|
||||
---
|
||||
|
||||
<!-- (Audio) Bob: Great! I'll send out a meeting invite and share the project timeline with everyone. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What will Bob do next?
|
||||
|
||||
## --answers--
|
||||
|
||||
He will send out a meeting invite and share the project timeline.
|
||||
|
||||
---
|
||||
|
||||
He will prepare a report on the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is not mentioned in the audio.
|
||||
|
||||
---
|
||||
|
||||
He will schedule a meeting with the team.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While Bob mentions sending a meeting invite, this option is too general and doesn't capture his specific plan to share the timeline as well.
|
||||
|
||||
---
|
||||
|
||||
He will ask for feedback on the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob is not seeking feedback.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that describe Bob's next actions.
|
||||
|
||||
`I'll send out a meeting invite` – This confirms he will schedule the meeting.
|
||||
|
||||
`Share the project timeline with everyone` – This shows he will also provide important project details.
|
||||
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 52.44,
|
||||
"finishTimestamp": 56.36
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.92,
|
||||
"dialogue": {
|
||||
"text": "Great. I'll send out a meeting invite and share the project timeline with everyone.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Bob",
|
||||
"opacity": 0,
|
||||
"startTime": 5.42
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
id: 67af26b82eb35209466f93ae
|
||||
title: Task 44
|
||||
challengeType: 22
|
||||
dashedName: task-44
|
||||
---
|
||||
|
||||
<!-- (Audio) Linda: No problem, Bob. I'm looking forward to working on this project. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`No problem, Bob. I'm BLANK BLANK BLANK working on this project.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`looking`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb is often used to describe the act of anticipating or being excited about something in the future. It ends with `-ing`.
|
||||
|
||||
---
|
||||
|
||||
`forward`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word indicates direction toward something in the future.
|
||||
|
||||
---
|
||||
|
||||
`to`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is a preposition that shows the connection between the verb and the thing being anticipated.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Forward` refers to a direction, often toward something in the future. It shows movement or anticipation of an upcoming event. For example:
|
||||
|
||||
`We are moving forward with the project.` – This means the project is progressing or continuing.
|
||||
|
||||
`Look forward to` means to eagerly anticipate something. It is often used when expressing excitement or positive expectation for an event or action that will happen in the future. It should be followed by a noun or the `-ing` form of a verb. For example:
|
||||
|
||||
- `I'm looking forward to the meeting.` – This shows your excitement about the meeting.
|
||||
|
||||
- `I'm looking forward to seeing you soon.` – This expresses your eagerness about meeting someone in the future.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 58.72,
|
||||
"finishTimestamp": 61.5
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.78,
|
||||
"dialogue": {
|
||||
"text": "No problem, Bob. I'm looking forward to working on this project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 4.28
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,58 @@
|
||||
---
|
||||
id: 67af33c72716c82c4d565f0f
|
||||
title: Task 45
|
||||
challengeType: 19
|
||||
dashedName: task-45
|
||||
---
|
||||
|
||||
# --instructions--
|
||||
|
||||
This task doesn't have audio. Read the question below and select the correct answer.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Which sentence uses the phrase `look forward to` correctly?
|
||||
|
||||
## --answers--
|
||||
|
||||
`I'm looking forward to finish the project by next week.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Look forward to` should be followed by a verb in its `-ing` form (e.g., `finishing` instead of `finish`).
|
||||
|
||||
---
|
||||
|
||||
`We are looking forward to see you soon.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Look forward to` should be followed by the `-ing` form of the verb, like `seeing`.
|
||||
|
||||
---
|
||||
|
||||
`I'm looking forward to meeting with the team tomorrow.`
|
||||
|
||||
---
|
||||
|
||||
`He looks forward to receive the report later today.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Look forward to` should be followed by a verb in its `-ing` form, like `receiving`.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Look forward to` is a phrasal verb that always needs to be followed by a **noun** or a **verb in its** `-ing` **form**. For example:
|
||||
|
||||
- `I'm looking forward to meeting with the team tomorrow.` – Here, `meeting` is the `-ing` form of the verb, making the sentence correct.
|
||||
|
||||
- `We are looking forward to the event next week.` – In this case, `event` is a noun, which is also correct.
|
||||
|
||||
Incorrect examples often use the base form of the verb instead of the `-ing` form. The correct answer follows this rule.
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67af348a5f1e3b2ed7cff509
|
||||
title: Task 46
|
||||
challengeType: 19
|
||||
dashedName: task-46
|
||||
---
|
||||
|
||||
<!-- (audio) Linda: No problem, Bob. I'm looking forward to working on this project. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Linda express in the conversation?
|
||||
|
||||
## --answers--
|
||||
|
||||
She is concerned about the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda's tone is positive, and she doesn't express concern.
|
||||
|
||||
---
|
||||
|
||||
She is unsure about the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda sounds confident and enthusiastic about working on the project.
|
||||
|
||||
---
|
||||
|
||||
She doesn't want to work on the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Linda sounds eager to work on the project.
|
||||
|
||||
---
|
||||
|
||||
She is excited about working on the project.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key words that show Linda's feelings about the project.
|
||||
|
||||
`No problem` – This suggests she is comfortable and willing to help.
|
||||
|
||||
`Looking forward to` – This phrase expresses excitement and anticipation for something in the future.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 58.82,
|
||||
"finishTimestamp": 61.4
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.58,
|
||||
"dialogue": {
|
||||
"text": "No problem, Bob. I'm looking forward to working on this project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 4.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67af35c80225e132c652185b
|
||||
title: Task 43
|
||||
challengeType: 22
|
||||
dashedName: task-43
|
||||
---
|
||||
|
||||
<!-- (audio) Linda: No problem, Bob. I'm looking forward to working on this project. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK BLANK, Bob. I'm looking forward to working on this project.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`No`
|
||||
|
||||
### --feedback--
|
||||
|
||||
The word is used to indicate a negative response or to reject something. It can also be used to express an absence or lack of something. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`problem`
|
||||
|
||||
### --feedback--
|
||||
|
||||
The word refers to a difficulty or issue that needs to be solved.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`No problem` is used to indicate that there is no difficulty or issue with something. It is commonly used to express that something is easy or that the speaker is happy to do it. For example:
|
||||
|
||||
`No problem, I can help you with that.` – This means the speaker is happy to assist and there are no difficulties involved.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-1.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 58.72,
|
||||
"finishTimestamp": 61.5
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.78,
|
||||
"dialogue": {
|
||||
"text": "No problem, Bob. I'm looking forward to working on this project.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Linda",
|
||||
"opacity": 0,
|
||||
"startTime": 4.28
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: 67af38efdf48173d0c0636b3
|
||||
title: Task 47
|
||||
challengeType: 22
|
||||
dashedName: task-47
|
||||
---
|
||||
|
||||
<!-- REVIEW -->
|
||||
|
||||
# --description--
|
||||
|
||||
This is a review of the entire dialogue you just studied.
|
||||
|
||||
# --instructions--
|
||||
|
||||
Place the following phrases in the correct spot:
|
||||
|
||||
`can also`, `Does that work`, `was thinking`, `good plan`, `No problem`, and `are great`.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Bob: We need to start planning our new mobile app project. Let's discuss the timeline. I BLANK we should aim to have the initial prototype ready in four weeks. Does that sound reasonable?`
|
||||
|
||||
`Linda: I think that's doable. We can work on the design sketches this week and then move on to wireframes.`
|
||||
|
||||
`Bob: Exactly. Once we have the wireframes, we can start collaborating with the developers to implement the front-end design.`
|
||||
|
||||
`Linda: Absolutely. And I BLANK prepare some user scenarios for testing, so we can ensure a smooth user experience.`
|
||||
|
||||
`Bob: Good idea. By the way, we need to allocate tasks among the team. I was thinking that you could lead the UX design, and I'll coordinate with the developers. BLANK for you?`
|
||||
|
||||
`Linda: That's a BLANK. I'll also keep you updated on the design progress, and we can schedule regular meetings to stay on track.`
|
||||
|
||||
`Bob: Perfect. Let's set a weekly meeting to review our progress. Would Friday morning work for you?`
|
||||
|
||||
`Linda: Sure, Friday mornings BLANK. It gives me a chance to review the week's work and plan for the next week.`
|
||||
|
||||
`Bob: Great! I'll send out a meeting invite and share the project timeline with everyone. Thanks for your input, Linda.`
|
||||
|
||||
`Linda: BLANK, Bob. I'm looking forward to working on this project.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`was thinking`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase is the `Past Continuous` form of a verb, often used to introduce an idea or suggestion. The first word indicates a past action, and the second word shows that the thought was in progress at a certain time.
|
||||
|
||||
---
|
||||
|
||||
`can also`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase is used to add another action or possibility. The first word is a verb showing ability, and the second word indicates an additional option.
|
||||
|
||||
---
|
||||
|
||||
`Does that work`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This three-word phrase is used to ask if a suggestion or proposal is acceptable. The first letter of the first word is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`good plan`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This phrase refers to a well-thought-out strategy or approach to achieving a goal.
|
||||
|
||||
---
|
||||
|
||||
`are great`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This phrase is used to describe something as excellent or very good. The first word is a verb, and the second is an adjective expressing a high level of quality.
|
||||
|
||||
---
|
||||
|
||||
`No problem`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase is used to express that something is not a burden or difficulty. It's often used to indicate that the speaker is happy to help or take care of something. The first letter of the first word is capitalized.
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
id: 67af429d29bc315537a8fcf8
|
||||
title: Task 48
|
||||
challengeType: 19
|
||||
dashedName: task-48
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
After the conversation with Linda, Bob sent an email to the team.
|
||||
|
||||
`Hi team,`
|
||||
|
||||
`I hope you're all doing well. Our first weekly meeting to review the mobile app project progress is scheduled for Friday morning at 9:00 AM. We'll go over the timeline, the prototype status, and the next steps for the design sketches and wireframes.`
|
||||
|
||||
`As we discussed, Linda will lead the UX design, and I'll be the one to coordinate with the developers. We'll also need to allocate tasks for the next phase, especially around the front-end design.`
|
||||
|
||||
`I'm excited to hear everyone's updates, and I'm confident these regular check-ins will help us stay focused and meet our deadlines. Looking forward to seeing you all!`
|
||||
|
||||
`Best,`
|
||||
|
||||
`Bob`
|
||||
|
||||
What is the main topic of Bob's email?
|
||||
|
||||
## --answers--
|
||||
|
||||
A meeting invite for the project.
|
||||
|
||||
---
|
||||
|
||||
Project updates on the new mobile app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email does not give updates about the project as it's not started yet.
|
||||
|
||||
---
|
||||
|
||||
A request for additional team members.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email does not mention recruiting additional team members.
|
||||
|
||||
---
|
||||
|
||||
A follow-up on the design sketches.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email mentions design sketches briefly, but the overall topic is about the meeting and progress review.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Look for key words that indicate the purpose of Bob's email.
|
||||
|
||||
`Our first weekly meeting... is scheduled for Friday morning at 9:00 AM` – This confirms that the email is about setting up a meeting.
|
||||
|
||||
`We'll go over the timeline, the prototype status, and the next steps` – This outlines what will be discussed in the meeting.
|
||||
|
||||
`Looking forward to seeing you all!` – This reinforces that the main focus is on gathering the team for a scheduled discussion.
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
id: 67af43f7fc63e958e481f14b
|
||||
title: Task 49
|
||||
challengeType: 19
|
||||
dashedName: task-49
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
After the conversation with Linda, Bob sent an email to the team.
|
||||
|
||||
`Hi team,`
|
||||
|
||||
`I hope you're all doing well. Our first weekly meeting to review the mobile app project progress is scheduled for Friday morning at 9:00 AM. We'll go over the timeline, the prototype status, and the next steps for the design sketches and wireframes.`
|
||||
|
||||
`As we discussed, Linda will lead the UX design, and I'll be the one to coordinate with the developers. We'll also need to allocate tasks for the next phase, especially around the front-end design.`
|
||||
|
||||
`I'm excited to hear everyone's updates, and I'm confident these regular check-ins will help us stay focused and meet our deadlines. Looking forward to seeing you all!`
|
||||
|
||||
`Best,`
|
||||
|
||||
`Bob`
|
||||
|
||||
What time is the weekly meeting scheduled for?
|
||||
|
||||
## --answers--
|
||||
|
||||
Friday at 10:00 AM.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email doesn't mention the meeting time is 10:00 AM.
|
||||
|
||||
---
|
||||
|
||||
Friday at 9:00 AM.
|
||||
|
||||
---
|
||||
|
||||
Thursday at 9:00 AM.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The meeting is not scheduled for Thursday.
|
||||
|
||||
---
|
||||
|
||||
Wednesday at 9:00 AM.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The correct day is not Wednesday.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
To find the time of the meeting, look for the part of the text that mentions when it was `scheduled`.
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
id: 67af45555bbf475c945f211f
|
||||
title: Task 50
|
||||
challengeType: 19
|
||||
dashedName: task-50
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
After the conversation with Linda, Bob sent an email to the team.
|
||||
|
||||
`Hi team,`
|
||||
|
||||
`I hope you're all doing well. Our first weekly meeting to review the mobile app project progress is scheduled for Friday morning at 9:00 AM. We'll go over the timeline, the prototype status, and the next steps for the design sketches and wireframes.`
|
||||
|
||||
`As we discussed, Linda will lead the UX design, and I'll be the one to coordinate with the developers. We'll also need to allocate tasks for the next phase, especially around the front-end design.`
|
||||
|
||||
`I'm excited to hear everyone's updates, and I'm confident these regular check-ins will help us stay focused and meet our deadlines. Looking forward to seeing you all!`
|
||||
|
||||
`Best,`
|
||||
|
||||
`Bob`
|
||||
|
||||
What does Bob plan to discuss in the meeting?
|
||||
|
||||
## --answers--
|
||||
|
||||
The timeline, prototype, design sketches, and wireframes.
|
||||
|
||||
---
|
||||
|
||||
Team roles and responsibilities.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Roles and responsibilities are briefly mentioned, but not the main focus of the meeting.
|
||||
|
||||
---
|
||||
|
||||
Team attendance at the meeting.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email does not mention attendance.
|
||||
|
||||
---
|
||||
|
||||
Budget for the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Budgeting is not mentioned in the email.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
To find what Bob plans to discuss, look for the sentence that starts with `We'll go over`.
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
id: 67af45e075d4cc5e536d055e
|
||||
title: Task 51
|
||||
challengeType: 19
|
||||
dashedName: task-51
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
After the conversation with Linda, Bob sent an email to the team.
|
||||
|
||||
`Hi team,`
|
||||
|
||||
`I hope you're all doing well. Our first weekly meeting to review the mobile app project progress is scheduled for Friday morning at 9:00 AM. We'll go over the timeline, the prototype status, and the next steps for the design sketches and wireframes.`
|
||||
|
||||
`As we discussed, Linda will lead the UX design, and I'll be the one to coordinate with the developers. We'll also need to allocate tasks for the next phase, especially around the front-end design.`
|
||||
|
||||
`I'm excited to hear everyone's updates, and I'm confident these regular check-ins will help us stay focused and meet our deadlines. Looking forward to seeing you all!`
|
||||
|
||||
`Best,`
|
||||
|
||||
`Bob`
|
||||
|
||||
Who will lead the UX design?
|
||||
|
||||
## --answers--
|
||||
|
||||
Both Bob and Linda
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email specifically mentions one person will lead the UX design.
|
||||
|
||||
---
|
||||
|
||||
Bob
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob will coordinate with the developers.
|
||||
|
||||
---
|
||||
|
||||
Linda
|
||||
|
||||
---
|
||||
|
||||
No one
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email clearly mentions someone as the one leading the UX design.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
To find the answer, look for the sentence that contains `lead the UX design` and see what is the person ssociated with this activity.
|
||||
@@ -0,0 +1,70 @@
|
||||
---
|
||||
id: 67af46a4ec8db360d8f0cc7a
|
||||
title: Task 52
|
||||
challengeType: 19
|
||||
dashedName: task-52
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
After the conversation with Linda, Bob sent an email to the team.
|
||||
|
||||
`Hi team,`
|
||||
|
||||
`I hope you're all doing well. Our first weekly meeting to review the mobile app project progress is scheduled for Friday morning at 9:00 AM. We'll go over the timeline, the prototype status, and the next steps for the design sketches and wireframes.`
|
||||
|
||||
`As we discussed, Linda will lead the UX design, and I'll be the one to coordinate with the developers. We'll also need to allocate tasks for the next phase, especially around the front-end design.`
|
||||
|
||||
`I'm excited to hear everyone's updates, and I'm confident these regular check-ins will help us stay focused and meet our deadlines. Looking forward to seeing you all!`
|
||||
|
||||
`Best,`
|
||||
|
||||
`Bob`
|
||||
|
||||
What does Bob believe will be the result of the regular check-ins?
|
||||
|
||||
## --answers--
|
||||
|
||||
They will improve the design of the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email doesn't suggest they will directly improve the app's design.
|
||||
|
||||
---
|
||||
|
||||
They will help the team finish the project faster.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email does not mention finishing the project faster.
|
||||
|
||||
---
|
||||
|
||||
They will help the team focus on the project and finihsh work before the deadlines.
|
||||
|
||||
---
|
||||
|
||||
They will provide opportunities for team-building.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The email does not mention team-building as the purpose of the check-ins.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Look for key details in the email that explain what Bob expects from the check-ins.
|
||||
|
||||
Pay special attention to the phrase that starts with `I'm confident these regular check-ins...`.
|
||||
@@ -0,0 +1,187 @@
|
||||
---
|
||||
id: 67b1aca09cf3a9ec7234c6fd
|
||||
title: "Dialogue 2: Code Review"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-2-code-review
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video below to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.3,
|
||||
"dialogue": {
|
||||
"text": "Mark, I reviewed your code for the new feature and it's looking good.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 4.54,
|
||||
"finishTime": 6.44,
|
||||
"dialogue": {
|
||||
"text": "It's well organized and works as expected.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 6.92,
|
||||
"finishTime": 10.66,
|
||||
"dialogue": {
|
||||
"text": "Thanks, Sarah. I made sure to keep the code clean and easy to read.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 10.98,
|
||||
"finishTime": 12.76,
|
||||
"dialogue": {
|
||||
"text": "That's great. Clean code is helpful.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 13.22,
|
||||
"finishTime": 16.68,
|
||||
"dialogue": {
|
||||
"text": "The comments you added in the code really helped the team understand what each part does.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 17.56,
|
||||
"finishTime": 21.76,
|
||||
"dialogue": {
|
||||
"text": "I'm glad you think so. I find it helps when we need to make changes later on.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 22.26,
|
||||
"finishTime": 25.86,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. I also like how you tested the code to make sure it doesn't have any errors.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 26.04,
|
||||
"finishTime": 27.54,
|
||||
"dialogue": {
|
||||
"text": "It makes our work more reliable.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 27.54,
|
||||
"finishTime": 30.74,
|
||||
"dialogue": {
|
||||
"text": "Thanks. Testing is important to catch problems early.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 31.08,
|
||||
"finishTime": 33.12,
|
||||
"dialogue": {
|
||||
"text": "Is there anything else you'd like me to improve on?",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 33.84,
|
||||
"finishTime": 37.76,
|
||||
"dialogue": {
|
||||
"text": "Yes. Let's work on speeding up the database queries. It'll make the app run faster.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 37.98,
|
||||
"finishTime": 41.02,
|
||||
"dialogue": {
|
||||
"text": "Got it. I'll start working on that and let you know when it's ready.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 41.38,
|
||||
"finishTime": 43.02,
|
||||
"dialogue": {
|
||||
"text": "Sounds great. Keep up the good work, Mark.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 43.66,
|
||||
"finishTime": 44.88,
|
||||
"dialogue": {
|
||||
"text": "Will do. Thanks, Sarah.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 45.38
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 45.88
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67b1acde9499a6ed8c01b135
|
||||
title: Task 53
|
||||
challengeType: 22
|
||||
dashedName: task-53
|
||||
---
|
||||
|
||||
<!-- (audio) Sarah: Mark, I reviewed your code for the new feature, and it's looking good. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Mark, I reviewed your BLANK for the new BLANK, and it's looking good.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`code`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to a set of instructions written in a programming language.
|
||||
|
||||
---
|
||||
|
||||
`feature`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to a distinct attribute or function of a program.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Code` refers to a set of instructions written in a programming language to perform a specific task. For example:
|
||||
|
||||
`The code makes the website load quickly.` - The sentence means that the instructions behind the website help it load faster.
|
||||
|
||||
`Feature` refers to a specific functionality or component of a program or software. For example:
|
||||
|
||||
`The new feature enables users to customize their settings.` - The sentence means that the new function allows users to change their settings.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0.46,
|
||||
"finishTimestamp": 3.76
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.3,
|
||||
"dialogue": {
|
||||
"text": "Mark, I reviewed your code for the new feature and it's looking good.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 4.8
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
id: 67b1be6f616adc19991819e6
|
||||
title: Task 54
|
||||
challengeType: 19
|
||||
dashedName: task-54
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Mark, I reviewed your code for the new feature, and it's looking good. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Sarah say about Mark's code?
|
||||
|
||||
## --answers--
|
||||
|
||||
It needs more work.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't mention that the code needs more work.
|
||||
|
||||
---
|
||||
|
||||
It looks good.
|
||||
|
||||
---
|
||||
|
||||
It's a bit confusing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't say the code is confusing.
|
||||
|
||||
---
|
||||
|
||||
It has a few bugs.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't mention any bugs.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Looking good` means that Sarah is satisfied with the quality of Mark's code. It's a positive statement indicating that the code is in good condition and doesn't need much improvement.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0.46,
|
||||
"finishTimestamp": 3.76
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.3,
|
||||
"dialogue": {
|
||||
"text": "Mark, I reviewed your code for the new feature and it's looking good.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 4.8
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67b1bfd4a309ef1da9b1be60
|
||||
title: Task 55
|
||||
challengeType: 22
|
||||
dashedName: task-55
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: It's well-organized and works as expected. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`It's BLANK and works BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`well-organized`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This describes something that is arranged in a clear and structured way. This is a compound word. Remember to use `-`
|
||||
|
||||
---
|
||||
|
||||
`as expected`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase means that the result is exactly what was anticipated or planned.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Well-organized` refers to something that is neatly arranged and easy to understand or use. For example:
|
||||
|
||||
`The presentation was well-organized, with each slide clearly explaining the key points.` - This means that the presentation was structured in a way that made it easy to follow and understand.
|
||||
|
||||
`As expected` means that something turned out exactly as it was predicted or planned. For example:
|
||||
|
||||
`The project was finished on time, as expected.` - This means the outcome of the project was exactly what was anticipated, without any surprises.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 3.7,
|
||||
"finishTimestamp": 5.9
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.2,
|
||||
"dialogue": {
|
||||
"text": "It's well-organized and works as expected.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 3.7
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
id: 67b1d55abbc79129344a55a8
|
||||
title: Task 56
|
||||
challengeType: 19
|
||||
dashedName: task-56
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: It's well-organized and works as expected. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Sarah say about the project?
|
||||
|
||||
## --answers--
|
||||
|
||||
It has some issues.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't mention any issues.
|
||||
|
||||
---
|
||||
|
||||
It is difficult to understand.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't say the project is difficult to understand.
|
||||
|
||||
---
|
||||
|
||||
It needs further testing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't mention testing.
|
||||
|
||||
---
|
||||
|
||||
It is well-organized and functions correctly.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Well-organized` means that the project is arranged clearly and logically, making it easy to use or understand. `Works as expected` means that the project is functioning as intended without any problems or surprises.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 3.7,
|
||||
"finishTimestamp": 5.9
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.2,
|
||||
"dialogue": {
|
||||
"text": "It's well-organized and works as expected.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 3.7
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,96 @@
|
||||
---
|
||||
id: 67b1d64e7cda992c0296fe7a
|
||||
title: Task 57
|
||||
challengeType: 22
|
||||
dashedName: task-57
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Thanks, Sarah. I made sure to keep the code clean and easy to read. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Thanks, Sarah. I BLANK BLANK BLANK keep the code clean and easy to read.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`made`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is the past tense of the verb `make`, indicating that the action was completed.
|
||||
|
||||
---
|
||||
|
||||
`sure`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to being confident or certain about something. It often follows `make` to express effort or intention.
|
||||
|
||||
---
|
||||
|
||||
`to`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is an infinitive marker used before a verb to indicate purpose or intention.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Make sure to` means to ensure or take action to do something carefully or correctly. It's used to express the idea that someone is taking steps to guarantee something happens. For example:
|
||||
|
||||
`I made sure to finish the project on time.` - This means you took actions to ensure that the project was completed on time.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.18,
|
||||
"finishTimestamp": 10.12
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Thanks, Sarah. I made sure to keep the code clean and easy to read.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67b1d8345211473169794a1d
|
||||
title: Task 58
|
||||
challengeType: 22
|
||||
dashedName: task-58
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Thanks, Sarah. I made sure to keep the code clean and easy to read. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Thanks, Sarah. I made sure to BLANK the code BLANK and easy to read.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`keep`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb means to maintain or continue something in a certain state or condition.
|
||||
|
||||
---
|
||||
|
||||
`clean`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to something that is free from errors or unnecessary parts, particularly in the context of code.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Keep the code clean` is often used to mean maintaining well-organized, readable, and error-free code. It implies that the code is written in a clear, structured way, making it easy to understand, debug, and modify. For example:
|
||||
|
||||
`It's important to keep the code clean by removing unnecessary comments and organizing functions properly.` - This means making sure the code is simple, well-structured, and easy to follow.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.18,
|
||||
"finishTimestamp": 10.12
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Thanks, Sarah. I made sure to keep the code clean and easy to read.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,104 @@
|
||||
---
|
||||
id: 67b1d8fcf1608833bdc06993
|
||||
title: Task 59
|
||||
challengeType: 19
|
||||
dashedName: task-59
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Thanks, Sarah. I made sure to keep the code clean and easy to read. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What was Mark's main goal when writing the code?
|
||||
|
||||
## --answers--
|
||||
|
||||
To make it faster.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark did not mention improving the speed.
|
||||
|
||||
---
|
||||
|
||||
To ensure it's shorter.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark did not mention making the code shorter.
|
||||
|
||||
---
|
||||
|
||||
To make it well-organized and easy to read.
|
||||
|
||||
---
|
||||
|
||||
To add more features.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark did not mention adding new features.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Mark's goal was to keep the code `clean` (well-organized, clear, and easy to understand) and `easy to read` (structured in a way that is simple for other programmers to follow).
|
||||
|
||||
These two qualities help in maintaining good coding practices and prevent future issues.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.18,
|
||||
"finishTimestamp": 10.12
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.94,
|
||||
"dialogue": {
|
||||
"text": "Thanks, Sarah. I made sure to keep the code clean and easy to read.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 5.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
id: 67b1da8af03f0f384749d71f
|
||||
title: Task 60
|
||||
challengeType: 22
|
||||
dashedName: task-60
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: That's great - clean code is helpful. The comments you added in the code really help the team understand what each part does. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK BLANK - clean code is helpful. The BLANK you added in the code really help the team understand what each part does.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`That's`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is a contraction of `That is`.
|
||||
|
||||
---
|
||||
|
||||
`great`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means something is very good or positive.
|
||||
|
||||
---
|
||||
|
||||
`comments`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These word in the plural form means explanatory notes added to the code to describe what it does, making it easier for others to understand.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`That's great` is a phrase used to express approval or happiness about something. It means that something is very positive or good. For example:
|
||||
|
||||
`That's great that you finished your task ahead of schedule.` - This means the speaker is happy or impressed with the accomplishment.
|
||||
|
||||
`Comments` in coding are notes written by the programmer to explain sections of the code. They help others (or the programmer in the future) understand what the code is doing. For example:
|
||||
|
||||
`The comments in the function explained how the algorithm worked step-by-step.` - This means the comments helped clarify the purpose of each part of the code.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 10.44,
|
||||
"finishTimestamp": 16.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.78,
|
||||
"dialogue": {
|
||||
"text": "That's great - clean code is helpful.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.24,
|
||||
"finishTime": 6.7,
|
||||
"dialogue": {
|
||||
"text": "The comments you added in the code really helped the team understand what each part does.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 7.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,115 @@
|
||||
---
|
||||
id: 67b1dbc920478f3bf71f3a86
|
||||
title: Task 61
|
||||
challengeType: 19
|
||||
dashedName: task-61
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: That's great - clean code is helpful. The comments you added in the code really help the team understand what each part does. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
How does Sarah support her positive feedback about the code?
|
||||
|
||||
## --answers--
|
||||
|
||||
She mentions the code's speed.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't mention the speed of the code.
|
||||
|
||||
---
|
||||
|
||||
She explains how the comments help the team understand the code.
|
||||
|
||||
---
|
||||
|
||||
She suggests adding more comments.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah does not suggest adding more comments.
|
||||
|
||||
---
|
||||
|
||||
She praises the complexity of the code.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah does not mention complexity.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that explain why Sarah finds the code helpful.
|
||||
|
||||
`Clean code is helpful` – This shows she has a positive opinion.
|
||||
|
||||
`The comments you added… really help the team understand what each part does` – This explains why she finds the code useful.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 10.44,
|
||||
"finishTimestamp": 16.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.78,
|
||||
"dialogue": {
|
||||
"text": "That's great - clean code is helpful.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.24,
|
||||
"finishTime": 6.7,
|
||||
"dialogue": {
|
||||
"text": "The comments you added in the code really helped the team understand what each part does.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 7.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
id: 67b1ddf392f98642178927d4
|
||||
title: Task 62
|
||||
challengeType: 19
|
||||
dashedName: task-62
|
||||
---
|
||||
|
||||
<!-- SPEAKING -->
|
||||
|
||||
<!-- (Audio) Sarah: That's great - clean code is helpful. The comments you added in the code really help the team understand what each part does. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Mark is happy with Sarah's feedback. What should he answer to express that?
|
||||
|
||||
## --answers--
|
||||
|
||||
`Thank you, but I think it needs more work.`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This response doesn't fully agree with Sarah's feedback. It suggests the code still needs improvements.
|
||||
|
||||
---
|
||||
|
||||
`I'm glad you think so.`
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
`I'm glad you think so` shows agreement with Sarah's positive feedback and acknowledges her praise for the clean code and helpful comments.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 10.44,
|
||||
"finishTimestamp": 16.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.78,
|
||||
"dialogue": {
|
||||
"text": "That's great - clean code is helpful.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.24,
|
||||
"finishTime": 6.7,
|
||||
"dialogue": {
|
||||
"text": "The comments you added in the code really helped the team understand what each part does.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 7.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: 67b1e06dd84171494a52bfa4
|
||||
title: Task 63
|
||||
challengeType: 22
|
||||
dashedName: task-63
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: I'm glad you think so. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I'm glad you BLANK BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`think`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is the verb used when expressing an opinion or belief about something.
|
||||
|
||||
---
|
||||
|
||||
`so`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to the idea or statement previously mentioned, in this case, the positive feedback Sarah gave.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Think so` is used to agree with or confirm something someone else has said. It is often used when someone expresses a belief or judgment, and you want to agree with that judgment. For example:
|
||||
|
||||
- Person 1: `The project is on track.`
|
||||
|
||||
- Person 2: `I think so.` - Here, `think so` shows that this person agrees with their colleague's opinion about the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 17.02,
|
||||
"finishTimestamp": 18.14
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.12,
|
||||
"dialogue": {
|
||||
"text": "I'm glad you think so.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 2.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67b1e32a197da650fbdcd7e8
|
||||
title: Task 64
|
||||
challengeType: 22
|
||||
dashedName: task-64
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: I find it helps when we need to make changes later on. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`I find it helps when we need to BLANK BLANK later on.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`make`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb means to perform or carry out an action.
|
||||
|
||||
---
|
||||
|
||||
`changes`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This refers to modifications made to something, often to improve or correct it.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Make changes` means to modify or alter something. It is commonly used in contexts where something needs to be adjusted or improved over time. For example:
|
||||
|
||||
`We will make changes to the design based on feedback.` - This means that adjustments or improvements will be made to the design according to the feedback received.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 18.42,
|
||||
"finishTimestamp": 21.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.8,
|
||||
"dialogue": {
|
||||
"text": "I find it helps when we need to make changes later on.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 4.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67b1e5d94993e9592af44aaa
|
||||
title: Task 65
|
||||
challengeType: 19
|
||||
dashedName: task-65
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: I find it helps when we need to make changes later on. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
How does Mark support his idea about the usefulness of the comments in the code?
|
||||
|
||||
## --answers--
|
||||
|
||||
He explains that the comments make it easier to make changes later on.
|
||||
|
||||
---
|
||||
|
||||
He says the comments are unnecessary for future updates.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark emphasizes that the comments are helpful, not that they are unnecessary.
|
||||
|
||||
---
|
||||
|
||||
He suggests removing the comments in future versions.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark does not suggest removing the comments.
|
||||
|
||||
---
|
||||
|
||||
He mentions that comments are only useful in the current version.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark talks about the comments being useful for future changes.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that explain why Mark finds comments useful.
|
||||
|
||||
`I find it helps` – This shows he sees value in using comments.
|
||||
|
||||
`When we need to make changes later on` – This explains that comments make future modifications easier.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 18.42,
|
||||
"finishTimestamp": 21.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.8,
|
||||
"dialogue": {
|
||||
"text": "I find it helps when we need to make changes later on.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 4.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,113 @@
|
||||
---
|
||||
id: 67b1e6b6f922765bcd595546
|
||||
title: Task 66
|
||||
challengeType: 22
|
||||
dashedName: task-66
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Absolutely. I also like how you tested the code to make sure it doesn't have any errors. It makes our work more reliable. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Absolutely. I also like how you tested the code to BLANK it doesn't have any errors. It makes our work BLANK BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`make sure`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase means to check or confirm that something is correct or done properly.
|
||||
|
||||
---
|
||||
|
||||
`more`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word is used to indicate a greater degree.
|
||||
|
||||
---
|
||||
|
||||
`reliable`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means that something can be trusted to work correctly and consistently.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Make sure` means to take action to confirm that something is correct or completed. For example:
|
||||
|
||||
`Please make sure the report is submitted before the deadline.` – This means checking and ensuring the report is turned in on time.
|
||||
|
||||
`Reliable` means that something or someone can be trusted to perform well or to be consistent over time. For example:
|
||||
|
||||
`The server is reliable; it has been running without any issues for months.` - This means the server works consistently and doesn't cause problems.
|
||||
|
||||
`More reliable` means that something has become even more trustworthy or dependable. For example:
|
||||
|
||||
`The new software update makes the app more reliable.` - This means the app has become more trustworthy or stable after the update.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.42,
|
||||
"finishTimestamp": 27
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.3,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. I also like how you tested the code to make sure it doesn't have any errors.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 5.08,
|
||||
"finishTime": 6.58,
|
||||
"dialogue": {
|
||||
"text": "It makes our work more reliable.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 7.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,115 @@
|
||||
---
|
||||
id: 67b1e9d4a9985764d9c2b556
|
||||
title: Task 67
|
||||
challengeType: 19
|
||||
dashedName: task-67
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Absolutely. I also like how you tested the code to make sure it doesn't have any errors. It makes our work more reliable. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Sarah appreciate about how Mark approached testing the code?
|
||||
|
||||
## --answers--
|
||||
|
||||
Mark tested the code to confirm it worked correctly and had no errors.
|
||||
|
||||
---
|
||||
|
||||
Mark added new features to the code during the testing process.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't talk about adding features during testing.
|
||||
|
||||
---
|
||||
|
||||
Mark only tested the code for visual appearance.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah mentions that Mark tested the code for errors, not just visual elements.
|
||||
|
||||
---
|
||||
|
||||
Mark worked quickly to test the code without checking for errors.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah highlights that testing for errors is key to making their work more reliable, not just speed.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that explain what Sarah values about Mark's testing.
|
||||
|
||||
`Tested the code to make sure it doesn't have any errors` – This shows that Mark focused on error prevention.
|
||||
|
||||
`Makes our work more reliable` – This explains why thorough testing is important.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 21.42,
|
||||
"finishTimestamp": 27
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.3,
|
||||
"dialogue": {
|
||||
"text": "Absolutely. I also like how you tested the code to make sure it doesn't have any errors.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 5.08,
|
||||
"finishTime": 6.58,
|
||||
"dialogue": {
|
||||
"text": "It makes our work more reliable.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 7.08
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67b1eb878cc95b69e05822b6
|
||||
title: Task 68
|
||||
challengeType: 22
|
||||
dashedName: task-68
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Thanks. Testing is important to catch problems early. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Thanks. Testing is important to BLANK BLANK early.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`catch`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to find or notice something, often before it becomes a bigger issue.
|
||||
|
||||
---
|
||||
|
||||
`problems`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to issues or difficulties that need to be addressed or solved.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Catch` in this context means to discover or identify something, especially before it becomes too serious. For example:
|
||||
|
||||
`The manager was quick to catch the mistakes in the report.` - This means that the manager noticed the mistakes early before they could cause more issues.
|
||||
|
||||
`Catch problems` means to find problems or issues, often early enough to fix them before they get worse. For example:
|
||||
|
||||
`Testing the system helps to catch problems before they affect users.` - This means that the testing process allows them to discover problems before they cause harm to users or the system.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 27,
|
||||
"finishTimestamp": 30.2
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.2,
|
||||
"dialogue": {
|
||||
"text": "Thanks. Testing is important to catch problems early.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 4.7
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
id: 67b1ecb619ae816e3d1c77db
|
||||
title: Task 69
|
||||
challengeType: 19
|
||||
dashedName: task-69
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Thanks. Testing is important to catch problems early. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Why does Mark think testing is important?
|
||||
|
||||
## --answers--
|
||||
|
||||
Testing ensures that the product looks good and works as expected.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark doesn't focus on testing to check if the product looks good or works as expected.
|
||||
|
||||
---
|
||||
|
||||
Testing helps to identify issues before they become bigger problems.
|
||||
|
||||
---
|
||||
|
||||
Testing helps to speed up the development process.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark doesn't mention that testing is important for making the development process faster.
|
||||
|
||||
---
|
||||
|
||||
Testing is only important for final product releases.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark talks about the importance of testing early in the process, not just before a final release.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
By saying `catch problems early`, Mark means testing can help find problems in the early stage before they become bigger ones.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 27,
|
||||
"finishTimestamp": 30.2
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.2,
|
||||
"dialogue": {
|
||||
"text": "Thanks. Testing is important to catch problems early.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 4.7
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67b1edf306ac9d720066d78d
|
||||
title: Task 70
|
||||
challengeType: 22
|
||||
dashedName: task-70
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Is there anything else you'd like me to improve on? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Is there anything else you'd like me to BLANK BLANK?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`improve`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb means to make something better or to enhance it in some way.
|
||||
|
||||
---
|
||||
|
||||
`on`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This preposition is used to indicate the focus of improvement or change.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Improve` means to make something better, enhance its quality, or fix issues. For example:
|
||||
|
||||
`She wants to improve her coding skills.` - This means that she wants to make her coding skills better by learning more or practicing more.
|
||||
|
||||
`Improve on` is used when talking about making something better than it was before. It focuses on improving a specific aspect or area. For example:
|
||||
|
||||
`He wants to improve on his previous performance in the competition.` - This means he wants to do better than he did before in the competition.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 30.24,
|
||||
"finishTimestamp": 32.58
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.34,
|
||||
"dialogue": {
|
||||
"text": "Is there anything else you'd like me to improve on?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 3.84
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,109 @@
|
||||
---
|
||||
id: 67b2bb2c55db7018a4719406
|
||||
title: Task 71
|
||||
challengeType: 22
|
||||
dashedName: task-71
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Yes, let's work on speeding up the database queries. It'll make the app run faster. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Yes, let's work on BLANK the BLANK BLANK. It'll make the app run faster.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`speeding`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These two words together refer to making something go faster or improving efficiency. The first word is a verb in its `-ing` form, and the second word is a preposition that indicates an increase in speed.
|
||||
|
||||
---
|
||||
|
||||
`database`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This refers to a structured collection of data that is stored and accessed electronically.
|
||||
|
||||
---
|
||||
|
||||
`queries`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word in the plural form refers to requests for data or information from a database.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Speed up` means to increase the speed of something or make it happen faster. For example:
|
||||
|
||||
`We need to speed up the website to improve the user experience.` - This means you need to make the website load faster.
|
||||
|
||||
`Database queries` refers to the requests made to a database to retrieve or modify data. These queries are written in a language like SQL (Structured Query Language) and are essential for interacting with the database. For example:
|
||||
|
||||
`The database queries are running slow, causing delays in loading the page.` - This means the requests to the database are taking too long to process, which affects the performance of the application.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 33.1,
|
||||
"finishTimestamp": 37.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.42,
|
||||
"dialogue": {
|
||||
"text": "Yes. Let's work on speeding up the database queries.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.76,
|
||||
"finishTime": 5.12,
|
||||
"dialogue": {
|
||||
"text": "It'll make the app run faster.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 5.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,97 @@
|
||||
---
|
||||
id: 67b2bca04ca3531ce94de51a
|
||||
title: Task 72
|
||||
challengeType: 22
|
||||
dashedName: task-72
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Yes, let's work on speeding up the database queries. It'll make the app run faster. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Yes, let's work on speeding up the database queries. It'll make the app BLANK BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`run`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb means to operate or function, often referring to software or applications.
|
||||
|
||||
---
|
||||
|
||||
`faster`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means at a greater speed, indicating improved performance or efficiency.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Run faster` means to operate more quickly and efficiently. In the context of software, it refers to improving performance so that the application processes tasks in less time. For example:
|
||||
|
||||
`Optimizing the code helped the program run faster.` - This means that improvements in the code made the program operate more efficiently.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 33.1,
|
||||
"finishTimestamp": 37.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.42,
|
||||
"dialogue": {
|
||||
"text": "Yes. Let's work on speeding up the database queries.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.76,
|
||||
"finishTime": 5.12,
|
||||
"dialogue": {
|
||||
"text": "It'll make the app run faster.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 5.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,114 @@
|
||||
---
|
||||
id: 67b2f20700c45e3c6e39a673
|
||||
title: Task 73
|
||||
challengeType: 19
|
||||
dashedName: task-73
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Yes, let's work on speeding up the database queries. It'll make the app run faster. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is going to improve the app's performance?
|
||||
|
||||
## --answers--
|
||||
|
||||
Improving the app's user interface.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The conversation is not about the user interface.
|
||||
|
||||
---
|
||||
|
||||
Adding more features to the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah doesn't mention adding more features.
|
||||
|
||||
---
|
||||
|
||||
Increasing the speed of the database queries.
|
||||
|
||||
---
|
||||
|
||||
Updating the app's design.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah is not talking about updating the design.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that explain what will improve the app's performance.
|
||||
|
||||
- `work on speeding up the database queries` – This directly states the focus on improving query speed.
|
||||
- `make the app run faster` – This explains how improving database queries will enhance performance.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 33.1,
|
||||
"finishTimestamp": 37.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.42,
|
||||
"dialogue": {
|
||||
"text": "Yes. Let's work on speeding up the database queries.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.76,
|
||||
"finishTime": 5.12,
|
||||
"dialogue": {
|
||||
"text": "It'll make the app run faster.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 5.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,99 @@
|
||||
---
|
||||
id: 67b2f4c60e993343e5f499e6
|
||||
title: Task 74
|
||||
challengeType: 19
|
||||
dashedName: task-74
|
||||
---
|
||||
|
||||
<!-- SPEAKING -->
|
||||
|
||||
<!-- (Audio) Sarah: Yes, let's work on speeding up the database queries. It'll make the app run faster. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Mark is ready to take action. What should he answer?
|
||||
|
||||
## --answers--
|
||||
|
||||
`Got it. I'll start working on that.`
|
||||
|
||||
---
|
||||
|
||||
`Thanks for the explanation. I'll think about it`
|
||||
|
||||
### --feedback--
|
||||
|
||||
Here you're acknowledging that Sarah provides a detailed explanation, which is not the case in this context. Sarah is directly suggesting an action.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Got it` is a casual, concise way to confirm understanding and agreement. In this context, it shows that you acknowledge Sarah's suggestion about improving the app's performance by speeding up the database queries.
|
||||
|
||||
`Thanks for the explanation` is more appropriate when you need clarification or when someone is explaining something new, but in this case, Sarah is making a suggestion, not explaining something in detail.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 33.1,
|
||||
"finishTimestamp": 37.22
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.42,
|
||||
"dialogue": {
|
||||
"text": "Yes. Let's work on speeding up the database queries.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 3.76,
|
||||
"finishTime": 5.12,
|
||||
"dialogue": {
|
||||
"text": "It'll make the app run faster.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 5.62
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67b2f6ded80a5349b4cdb55f
|
||||
title: Task 75
|
||||
challengeType: 22
|
||||
dashedName: task-75
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Got it. I'll start working on that and let you know when it's ready. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK. I'll start working on that and BLANK when it's ready.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Got it`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These two words together indicate understanding or acknowledgment. The first word is a past tense verb, and the second word shows possession or completion. This phrase is often used to confirm that someone has received and understood information.
|
||||
|
||||
---
|
||||
|
||||
`let you know`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This three-word phrase means to inform someone or provide them with information.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Got it` is an informal way of acknowledging that you've understood something. It's a quick response showing comprehension and agreement. For example:
|
||||
|
||||
`Got it, I'll handle it.` - This means you understand the request and is agreeing to take care of it.
|
||||
|
||||
`Let you know` means to tell someone about something in the future. It shows that you will keep someone informed. For example:
|
||||
|
||||
`I'll let you know when I finish the report.` - This means you will update the person with information when the task is complete.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 37.44,
|
||||
"finishTimestamp": 40.48
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.04,
|
||||
"dialogue": {
|
||||
"text": "Got it. I'll start working on that and let you know when it's ready.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 4.54
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,108 @@
|
||||
---
|
||||
id: 67b2f7af2658a24c24d7679e
|
||||
title: Task 76
|
||||
challengeType: 19
|
||||
dashedName: task-76
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Got it. I'll start working on that and let you know when it's ready. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Mark mean?
|
||||
|
||||
## --answers--
|
||||
|
||||
He will begin the task and keep Sarah updated on its progress.
|
||||
|
||||
---
|
||||
|
||||
He will finish the task quickly.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark does not mention how fast he will complete the task.
|
||||
|
||||
---
|
||||
|
||||
He is unsure about how to start the task.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark is confident and already committed to starting the task.
|
||||
|
||||
---
|
||||
|
||||
He will start working on the task when he's ready.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark explicitly states he will begin working on the task now, not later when he feels ready.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that show Mark's understanding and commitment to the task.
|
||||
|
||||
`Got it.` – This phrase indicates that he agrees with Sarah and understands what needs to be done.
|
||||
|
||||
`I'll start working on that` – This confirms that he is beginning the task right away.
|
||||
|
||||
`And let you know when it's ready` – This shows he will keep Sarah updated on its progress.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 37.44,
|
||||
"finishTimestamp": 40.48
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 4.04,
|
||||
"dialogue": {
|
||||
"text": "Got it. I'll start working on that and let you know when it's ready.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 4.54
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67b2f8e6655a944fea3b2659
|
||||
title: Task 77
|
||||
challengeType: 22
|
||||
dashedName: task-77
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Sounds great! Keep up the good work, Mark. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK BLANK! Keep up the good work, Mark.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Sounds`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is used to express what something seems like based on what you hear. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`great`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word describes something as very good or impressive.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Sounds great` is a common phrase used to express approval or agreement. It's often used when you think something is a good idea or plan. For example:
|
||||
|
||||
`The proposal sounds great!` - This means the proposal seems like a good idea.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 40.54,
|
||||
"finishTimestamp": 42.48
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.94,
|
||||
"dialogue": {
|
||||
"text": "Sounds great. Keep up the good work, Mark.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 3.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,80 @@
|
||||
---
|
||||
id: 67b2fbd2e2edc358536c2ebf
|
||||
title: Task 78
|
||||
challengeType: 22
|
||||
dashedName: task-78
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Sounds great! Keep up the good work, Mark. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Sounds great! BLANK the good work, Mark.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Keep up`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These two words together mean to continue doing something well or at the same level. The first word is a verb, and the second word is a preposition that suggests maintaining progress or effort.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Keep up` means to continue or maintain something, especially when it's done well. It's often used to motivate someone to maintain their efforts or achievements. For example:
|
||||
|
||||
`Keep up the great work!` - This means to continue doing something well or successfully.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 40.54,
|
||||
"finishTimestamp": 42.48
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.94,
|
||||
"dialogue": {
|
||||
"text": "Sounds great. Keep up the good work, Mark.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 3.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
id: 67b2fcd04c29685b48d0fb67
|
||||
title: Task 79
|
||||
challengeType: 19
|
||||
dashedName: task-79
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Sounds great! Keep up the good work, Mark. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Sarah encouraging Mark to do?
|
||||
|
||||
## --answers--
|
||||
|
||||
Stop working so hard.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah is not suggesting Mark stop working hard.
|
||||
|
||||
---
|
||||
|
||||
Maintain the same speed in his work.
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Keep up the good work` refers to maintaining the quality of work, not the speed.
|
||||
|
||||
---
|
||||
|
||||
Continue doing well in his work.
|
||||
|
||||
---
|
||||
|
||||
Try something new in his work.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah's words imply that Mark should continue doing what he's already doing.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Keep up the good work` means to continue performing well, to maintain the quality of one's work. Sarah is expressing approval of Mark's current work and motivating him to continue it.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 40.54,
|
||||
"finishTimestamp": 42.48
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.94,
|
||||
"dialogue": {
|
||||
"text": "Sounds great. Keep up the good work, Mark.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 3.44
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: 67b2ffe092d1a263d380dbae
|
||||
title: Task 80
|
||||
challengeType: 22
|
||||
dashedName: task-80
|
||||
---
|
||||
|
||||
<!-- (Audio) Mark: Will do. Thanks, Sarah! -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK BLANK. Thanks, Sarah!`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Will`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used here to indicate future action. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`do`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means to carry out or complete a task.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Will do` is used to express agreement to complete a task or take action. It is often used to show willingness or readiness to do something. For example:
|
||||
|
||||
- Person 1: `I need those reports by 5 PM.`
|
||||
|
||||
- Person 2: `Will do.` - This person will take care of it.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 42.82,
|
||||
"finishTimestamp": 44.34
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.52,
|
||||
"dialogue": {
|
||||
"text": "Will do. Thanks, Sarah.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 3.02
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,132 @@
|
||||
---
|
||||
id: 67b3022721bb7c6a5fcb135b
|
||||
title: Task 81
|
||||
challengeType: 19
|
||||
dashedName: task-81
|
||||
---
|
||||
|
||||
<!-- (Audio) Sarah: Sounds great! Keep up the good work, Mark. -->
|
||||
|
||||
<!-- (Audio) Mark: Will do. Thanks, Sarah! -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Mark agreeing to do in response to Sarah's encouragement?
|
||||
|
||||
## --answers--
|
||||
|
||||
He agrees to continue doing good work.
|
||||
|
||||
---
|
||||
|
||||
He agrees to finish the project immediately.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark is not specifically agreeing to finish the project immediately.
|
||||
|
||||
---
|
||||
|
||||
He asks Sarah for further instructions.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Mark is not asking for more instructions.
|
||||
|
||||
---
|
||||
|
||||
He thanks Sarah for the feedback.
|
||||
|
||||
### --feedback--
|
||||
|
||||
He thanks her feedback, but that's not related to the action he's going to take.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Will do` indicates Mark's agreement to continue performing well, as Sarah encouraged him to `keep up the good work`. It's an informal, positive response showing his readiness to keep working at a high standard.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company2-center.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.4
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-2.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 40.64,
|
||||
"finishTimestamp": 44.44
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.04,
|
||||
"dialogue": {
|
||||
"text": "Sounds great. Keep up the good work, Mark.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Sarah",
|
||||
"opacity": 0,
|
||||
"startTime": 3.36
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 1,
|
||||
"startTime": 3.36
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"startTime": 3.68,
|
||||
"finishTime": 4.9,
|
||||
"dialogue": {
|
||||
"text": "Will do. Thanks, Sarah.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Mark",
|
||||
"opacity": 0,
|
||||
"startTime": 5.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
id: 67b328dbb081d0b87e5429ba
|
||||
title: Task 82
|
||||
challengeType: 22
|
||||
dashedName: task-82
|
||||
---
|
||||
|
||||
<!-- REVIEW -->
|
||||
|
||||
# --description--
|
||||
|
||||
This is a review of the entire dialogue you just studied.
|
||||
|
||||
# --instructions--
|
||||
|
||||
Place the following phrases in the correct spot:
|
||||
|
||||
`make changes`, `speeding up`, `reliable`, `looking good`, `keep up`, and `catch`.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Sarah: Mark, I reviewed your code for the new feature, and it's BLANK. It's well-organized and works as expected.`
|
||||
|
||||
`Mark: Thanks, Sarah. I made sure to keep the code clean and easy to read.`
|
||||
|
||||
`Sarah: That's great - clean code is helpful. The comments you added in the code really help the team understand what each part does.`
|
||||
|
||||
`Mark: I'm glad you think so. I find it helps when we need to BLANK later on.`
|
||||
|
||||
`Sarah: Absolutely. I also like how you tested the code to make sure it doesn't have any errors. It makes our work more BLANK.`
|
||||
|
||||
`Mark: Thanks. Testing is important to BLANK problems early. Is there anything else you'd like me to improve on?`
|
||||
|
||||
`Sarah: Yes, let's work on BLANK the database queries. It'll make the app run faster.`
|
||||
|
||||
`Mark: Got it. I'll start working on that and let you know when it's ready.`
|
||||
|
||||
`Sarah: Sounds great! BLANK the good work, Mark.`
|
||||
|
||||
`Mark: Will do. Thanks, Sarah!`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`looking good`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase means that the code is in a good state, suggesting it's well-written and ready for use. The first word ends with `-ing`.
|
||||
|
||||
---
|
||||
|
||||
`make changes`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase means to alter or modify something, often used when referring to code improvements.
|
||||
|
||||
---
|
||||
|
||||
`reliable`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This means dependable or consistent, often used to describe code that works without errors or crashes.
|
||||
|
||||
---
|
||||
|
||||
`catch`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This means to identify or notice something, like a problem or error, early in the process.
|
||||
|
||||
---
|
||||
|
||||
`speeding up`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase means making something faster, in this case, improving the speed of database queries. The first word ends with `-ing`.
|
||||
|
||||
---
|
||||
|
||||
`Keep up`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These two words together mean to continue doing something at the same level or pace. The first word is a verb, and the second word is a preposition that suggests maintaining progress or effort. The first letter is capitalized.
|
||||
@@ -0,0 +1,76 @@
|
||||
---
|
||||
id: 67b32f9ba790e9c984503c55
|
||||
title: Task 83
|
||||
challengeType: 19
|
||||
dashedName: task-83
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Following their conversation, Mark sent a document to Sarah to update her on the improvements.
|
||||
|
||||
`Overview`
|
||||
|
||||
`The goal was to improve the performance of our app by speeding up the database queries. This change will help the app run faster and more efficiently.`
|
||||
|
||||
`Actions Taken`
|
||||
|
||||
`- Code Optimization: I reviewed the code that handles the database queries and optimized it to reduce delays. This ensures faster data retrieval and overall better performance.`
|
||||
|
||||
`- Comments Added: To make the code easier to understand, I added comments explaining the logic behind the changes. It will help the team when reviewing the code and when we need to make changes later on.`
|
||||
|
||||
`- Testing: I ran a series of tests to verify that the changes worked as expected. This testing process also helps us catch problems early, ensuring that the app remains stable.`
|
||||
|
||||
`Results`
|
||||
|
||||
`The improved queries should now make the app run faster. It is a big step toward a more responsive system.`
|
||||
|
||||
What is the goal of the changes Mark is making?
|
||||
|
||||
## --answers--
|
||||
|
||||
To fix bugs in the database.
|
||||
|
||||
### --feedback--
|
||||
|
||||
There is no mention of fixing bugs.
|
||||
|
||||
---
|
||||
|
||||
To speed up the database queries and improve the performance of the app.
|
||||
|
||||
---
|
||||
|
||||
To add more features to the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The changes don't focus on adding new features.
|
||||
|
||||
---
|
||||
|
||||
To add more comments to the code.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Although comments are added to help understand the code, this is not the main goal of the changes.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
Look for key details in the text that describe the purpose of Mark's changes.
|
||||
|
||||
Pay attention to the sentence that starts with `The goal was to improve ...` – This directly states the reason for the updates.
|
||||
|
||||
Also, pay attento to the sentence `This change will help...` – This reinforces that the focus is on performance improvements.
|
||||
@@ -0,0 +1,76 @@
|
||||
---
|
||||
id: 67b3348f2358b3d72ab41995
|
||||
title: Task 84
|
||||
challengeType: 19
|
||||
dashedName: task-84
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Following their conversation, Mark sent a document to Sarah to update her on the improvements.
|
||||
|
||||
`Overview`
|
||||
|
||||
`The goal was to improve the performance of our app by speeding up the database queries. This change will help the app run faster and more efficiently.`
|
||||
|
||||
`Actions Taken`
|
||||
|
||||
`- Code Optimization: I reviewed the code that handles the database queries and optimized it to reduce delays. This ensures faster data retrieval and overall better performance.`
|
||||
|
||||
`- Comments Added: To make the code easier to understand, I added comments explaining the logic behind the changes. It will help the team when reviewing the code and when we need to make changes later on.`
|
||||
|
||||
`- Testing: I ran a series of tests to verify that the changes worked as expected. This testing process also helps us catch problems early, ensuring that the app remains stable.`
|
||||
|
||||
`Results`
|
||||
|
||||
`The improved queries should now make the app run faster. It is a big step toward a more responsive system.`
|
||||
|
||||
How does Mark help the team understand the changes made in the code?
|
||||
|
||||
## --answers--
|
||||
|
||||
By adding comments to the code explaining the changes.
|
||||
|
||||
---
|
||||
|
||||
By sending the code through email.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The documentation does not mention sending the code through email.
|
||||
|
||||
---
|
||||
|
||||
By discussing the changes in a meeting.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While meetings can help with understanding changes, Mark emphasizes another way.
|
||||
|
||||
---
|
||||
|
||||
By creating a detailed document on the changes.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The focus is not on creating a separate document for the team.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Look for key details in the text that explain how Mark helps the team understand the changes.
|
||||
|
||||
`I added comments explaining the logic behind the changes.` – This directly states how Mark makes the code easier to understand.
|
||||
|
||||
`It will help the team when reviewing the code and when we need to make changes later on.` – This confirms that the comments are meant to assist the team.
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
id: 67b335626b775ed9e802dc9d
|
||||
title: Task 85
|
||||
challengeType: 19
|
||||
dashedName: task-85
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Following their conversation, Mark sent a document to Sarah to update her on the improvements.
|
||||
|
||||
`Overview`
|
||||
|
||||
`The goal was to improve the performance of our app by speeding up the database queries. This change will help the app run faster and more efficiently.`
|
||||
|
||||
`Actions Taken`
|
||||
|
||||
`- Code Optimization: I reviewed the code that handles the database queries and optimized it to reduce delays. This ensures faster data retrieval and overall better performance.`
|
||||
|
||||
`- Comments Added: To make the code easier to understand, I added comments explaining the logic behind the changes. It will help the team when reviewing the code and when we need to make changes later on.`
|
||||
|
||||
`- Testing: I ran a series of tests to verify that the changes worked as expected. This testing process also helps us catch problems early, ensuring that the app remains stable.`
|
||||
|
||||
`Results`
|
||||
|
||||
`The improved queries should now make the app run faster. It is a big step toward a more responsive system.`
|
||||
|
||||
What is the purpose of the testing Mark performed?
|
||||
|
||||
## --answers--
|
||||
|
||||
To verify that the changes worked as expected and catch problems early.
|
||||
|
||||
---
|
||||
|
||||
To test if the app is faster than before.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The document doesn't mention speed testing.
|
||||
|
||||
---
|
||||
|
||||
To check the database queries for errors.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The focus in the document is not on checking for errors in the queries.
|
||||
|
||||
---
|
||||
|
||||
To test the new features added to the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The testing in the document is not focused on testing new features.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
To find the correct answer, focus on the testing details Mark provides.
|
||||
|
||||
Pay attention to `I ran a series of...` and `This testing process also ` – Both sections of the text will help you understand the purpose of the testing: identifying issues before they become bigger problems.
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
id: 67b336b2abc639dda752f06f
|
||||
title: Task 86
|
||||
challengeType: 19
|
||||
dashedName: task-86
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Following their conversation, Mark sent a document to Sarah to update her on the improvements.
|
||||
|
||||
`Overview`
|
||||
|
||||
`The goal was to improve the performance of our app by speeding up the database queries. This change will help the app run faster and more efficiently.`
|
||||
|
||||
`Actions Taken`
|
||||
|
||||
`- Code Optimization: I reviewed the code that handles the database queries and optimized it to reduce delays. This ensures faster data retrieval and overall better performance.`
|
||||
|
||||
`- Comments Added: To make the code easier to understand, I added comments explaining the logic behind the changes. It will help the team when reviewing the code and when we need to make changes later on.`
|
||||
|
||||
`- Testing: I ran a series of tests to verify that the changes worked as expected. This testing process also helps us catch problems early, ensuring that the app remains stable.`
|
||||
|
||||
`Results`
|
||||
|
||||
`The improved queries should now make the app run faster. It is a big step toward a more responsive system.`
|
||||
|
||||
What did Mark do to optimize the performance of the app?
|
||||
|
||||
## --answers--
|
||||
|
||||
He added more comments to the code.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Adding comments helps with understanding the code, but it doesn't focus on performance optimization.
|
||||
|
||||
---
|
||||
|
||||
He added new features to the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
There is no mention of adding new features.
|
||||
|
||||
---
|
||||
|
||||
He conducted tests to ensure everything was working.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While testing is part of the process, the optimization of performance is not specifically related to testing.
|
||||
|
||||
---
|
||||
|
||||
He reviewed and optimized the code handling database queries.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
To find the correct answer, focus on the action Mark lists regarding the optimization.
|
||||
|
||||
Pay attention to `I reviewed the code that handles...` and `This ensures faster...` – These phrases will help you understand how he optimized the platform.
|
||||
@@ -0,0 +1,74 @@
|
||||
---
|
||||
id: 67b3387d323f1be321f52e7b
|
||||
title: Task 87
|
||||
challengeType: 19
|
||||
dashedName: task-87
|
||||
---
|
||||
|
||||
<!-- READING -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Read the text and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
Following their conversation, Mark sent a document to Sarah to update her on the improvements.
|
||||
|
||||
`Overview`
|
||||
|
||||
`The goal was to improve the performance of our app by speeding up the database queries. This change will help the app run faster and more efficiently.`
|
||||
|
||||
`Actions Taken`
|
||||
|
||||
`- Code Optimization: I reviewed the code that handles the database queries and optimized it to reduce delays. This ensures faster data retrieval and overall better performance.`
|
||||
|
||||
`- Comments Added: To make the code easier to understand, I added comments explaining the logic behind the changes. It will help the team when reviewing the code and when we need to make changes later on.`
|
||||
|
||||
`- Testing: I ran a series of tests to verify that the changes worked as expected. This testing process also helps us catch problems early, ensuring that the app remains stable.`
|
||||
|
||||
`Results`
|
||||
|
||||
`The improved queries should now make the app run faster. It is a big step toward a more responsive system.`
|
||||
|
||||
How does Mark describe the result of the changes?
|
||||
|
||||
## --answers--
|
||||
|
||||
The improved queries should make the app run faster.
|
||||
|
||||
---
|
||||
|
||||
The queries are now fully optimized and error-free.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The document discusses improved queries for faster performance, but there is no claim that the queries are completely error-free.
|
||||
|
||||
---
|
||||
|
||||
The app's overall performance will not change.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The primary aim of the changes is to improve performance, so this option does not match the result mentioned in the email.
|
||||
|
||||
---
|
||||
|
||||
The app now has additional features for faster performance.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The document focuses on optimizing the performance through faster database queries, not adding new features.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
To find the correct answer, focus on the result Mark provides.
|
||||
|
||||
Pay attention to `The improved queries should now... ` and you'll find out the main outcome of the changes.
|
||||
@@ -0,0 +1,250 @@
|
||||
---
|
||||
id: 67b447bd1ac6d92bed8e2279
|
||||
title: "Dialogue 3: Client Feedback"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-3-client-feedback
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video below to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": { "x": -25, "y": 0, "z": 1 }
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"position": { "x": 125, "y": 0, "z": 1 }
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1
|
||||
},
|
||||
"alwaysShowDialogue": true
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": { "x": 25, "y": 0, "z": 1 },
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"position": { "x": 70, "y": 0, "z": 1 },
|
||||
"startTime": 0.5
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.72,
|
||||
"dialogue": {
|
||||
"text": "Maria, I've reviewed the latest version of the mobile app and I'd like to share some feedback. Would now be a good time?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 7.34,
|
||||
"finishTime": 9.74,
|
||||
"dialogue": {
|
||||
"text": "Sure, Jim. I'm eager to hear what you think. How's it looking?",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 10.38,
|
||||
"finishTime": 15.28,
|
||||
"dialogue": {
|
||||
"text": "Overall, I think it's quite user-friendly. The design is clean and the navigation is straightforward.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 15.68,
|
||||
"finishTime": 19.8,
|
||||
"dialogue": {
|
||||
"text": "However, I've noticed that the app tends to lag a bit when switching between different sections.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 20.12,
|
||||
"finishTime": 21.1,
|
||||
"dialogue": {
|
||||
"text": "Could we work on that?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 21.68,
|
||||
"finishTime": 25.92,
|
||||
"dialogue": {
|
||||
"text": "I understand your point. We are aware of the lag and we're already addressing it in our next update.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 26.08,
|
||||
"finishTime": 27.32,
|
||||
"dialogue": {
|
||||
"text": "Thanks for bringing it to our attention.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 27.32,
|
||||
"finishTime": 30.54,
|
||||
"dialogue": {
|
||||
"text": "Also, I think the color scheme could use a bit more energy.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 30.94,
|
||||
"finishTime": 35.36,
|
||||
"dialogue": {
|
||||
"text": "It's currently a bit bland, especially for a tech-focused app. What do you think?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 35.82,
|
||||
"finishTime": 38.86,
|
||||
"dialogue": {
|
||||
"text": "I see where you're coming from. We've chosen a subtle color palette,",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 38.94,
|
||||
"finishTime": 40.94,
|
||||
"dialogue": {
|
||||
"text": "but maybe adding some brighter tones would help.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 41.3,
|
||||
"finishTime": 44.52,
|
||||
"dialogue": {
|
||||
"text": "I'll discuss it with the design team and see what we can do to make it more vibrant.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 45.06,
|
||||
"finishTime": 50.12,
|
||||
"dialogue": {
|
||||
"text": "Great. That would be helpful. Another thing, the login process seems a bit lengthy.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 50.22,
|
||||
"finishTime": 54.54,
|
||||
"dialogue": {
|
||||
"text": "It could be quicker, especially for returning users. Any thoughts on that?",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 54.54,
|
||||
"finishTime": 58.5,
|
||||
"dialogue": {
|
||||
"text": "That's a valid point. We're planning to implement a Remember Me feature,",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 58.9,
|
||||
"finishTime": 60.68,
|
||||
"dialogue": {
|
||||
"text": "which should help speed up the login process.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 60.96,
|
||||
"finishTime": 63.08,
|
||||
"dialogue": {
|
||||
"text": "I'll make sure it's prioritized for the next release.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 63.56,
|
||||
"finishTime": 67.9,
|
||||
"dialogue": {
|
||||
"text": "Excellent. I'm glad to hear that. I look forward to seeing the changes in the next version.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 68.24,
|
||||
"finishTime": 69.72,
|
||||
"dialogue": {
|
||||
"text": "Thanks for listening to my feedback.",
|
||||
"align": "left"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 70.32,
|
||||
"finishTime": 73.66,
|
||||
"dialogue": {
|
||||
"text": "Absolutely, Jim. We appreciate your insights. It helps us improve.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 73.88,
|
||||
"finishTime": 76.1,
|
||||
"dialogue": {
|
||||
"text": "If you have any more suggestions, feel free to reach out.",
|
||||
"align": "right"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"position": { "x": 125, "y": 0, "z": 1 },
|
||||
"startTime": 76.6
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": { "x": -25, "y": 0, "z": 1 },
|
||||
"startTime": 77.1
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,100 @@
|
||||
---
|
||||
id: 67b45fed9a8ec037502ba1a7
|
||||
title: Task 88
|
||||
challengeType: 22
|
||||
dashedName: task-88
|
||||
---
|
||||
|
||||
<!-- (audio) Jim: Maria, I've reviewed the latest version of the mobile app, and I'd like to share some feedback. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Maria, I've reviewed the BLANK version of the mobile app, and I'd like to BLANK some BLANK.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`latest`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word describes something that has just happened or is the most recent.
|
||||
|
||||
---
|
||||
|
||||
`share`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means to give something to others, such as information or ideas.
|
||||
|
||||
---
|
||||
|
||||
`feedback`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word refers to comments or suggestions about something.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Latest` refers to something that is the most recent or the newest in a series. For example:
|
||||
|
||||
`I tested the latest update of the app before the release.` - This means that you tested the most recent version of the app.
|
||||
|
||||
`Share feedback` means to give your thoughts, comments, or suggestions about something to help improve it. For example:
|
||||
|
||||
`I will share my feedback on the new software update in the next meeting.` - This means that you will provide your opinions or suggestions about the new update, which could help improve the software.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 4.46
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.46,
|
||||
"dialogue": {
|
||||
"text": "Maria, I've reviewed the latest version of the mobile app, and I'd like to share some feedback.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 0,
|
||||
"startTime": 5.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67b464dbdf4f8b3a378bd74e
|
||||
title: Task 89
|
||||
challengeType: 19
|
||||
dashedName: task-89
|
||||
---
|
||||
|
||||
<!-- (audio) Jim: Maria, I've reviewed the latest version of the mobile app, and I'd like to share some feedback. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Jim's main purpose?
|
||||
|
||||
## --answers--
|
||||
|
||||
He wants to discuss the app's future features.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not talking about future features, but rather the current version of the app.
|
||||
|
||||
---
|
||||
|
||||
He wants to give feedback on the latest version of the app.
|
||||
|
||||
---
|
||||
|
||||
He wants to ask Maria for her opinion on the app's design.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not asking for Maria's opinion, but rather sharing his own feedback.
|
||||
|
||||
---
|
||||
|
||||
He wants to ask Maria to help with testing the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not requesting help for testing.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that indicate Jim's main purpose.
|
||||
|
||||
`I've reviewed the latest version of the mobile app` – This shows he is focusing on the current version, not future features.
|
||||
|
||||
`I'd like to share some feedback` – This confirms that his main goal is to provide comments, not ask for opinions or request help.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 0,
|
||||
"finishTimestamp": 4.46
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 5.46,
|
||||
"dialogue": {
|
||||
"text": "Maria, I've reviewed the latest version of the mobile app, and I'd like to share some feedback.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 0,
|
||||
"startTime": 5.96
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,80 @@
|
||||
---
|
||||
id: 67b466d6babe693b6427352b
|
||||
title: Task 90
|
||||
challengeType: 22
|
||||
dashedName: task-90
|
||||
---
|
||||
|
||||
<!-- (audio) Jim: Would now be a good time? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Would now be a BLANK?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`good time`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This two-word phrase refers to an appropriate or convenient moment to do something.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Good time` is a phrase used to refer to a moment that is suitable or convenient for something to happen. For example:
|
||||
|
||||
`Is this a good time to talk about the project update?` - This means asking if the moment is right or convenient for discussing the project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.52,
|
||||
"finishTimestamp": 5.72
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.2,
|
||||
"dialogue": {
|
||||
"text": "Would now be a good time?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 0,
|
||||
"startTime": 2.7
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67b4681b40ac5c3c991e1f51
|
||||
title: Task 91
|
||||
challengeType: 19
|
||||
dashedName: task-91
|
||||
---
|
||||
|
||||
<!-- (audio) Jim: Would now be a good time? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Jim asking?
|
||||
|
||||
## --answers--
|
||||
|
||||
If it is a convenient time to talk.
|
||||
|
||||
---
|
||||
|
||||
If Maria is available to start a task.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not asking if Maria is available for a task.
|
||||
|
||||
---
|
||||
|
||||
If Maria has time to review the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not asking about reviewing the project.
|
||||
|
||||
---
|
||||
|
||||
If it's the right time for a meeting.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not specifically asking about a meeting.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
|
||||
# --explanation--
|
||||
|
||||
Jim is asking if now is a good time to talk.
|
||||
|
||||
`Would` makes the question more polite. Instead of asking directly, `Is now a good time?`, Jim says, `Would now be a good time?`.
|
||||
|
||||
This sounds softer and more polite because it shows respect for the other person's time.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 4.52,
|
||||
"finishTimestamp": 5.72
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 2.2,
|
||||
"dialogue": {
|
||||
"text": "Would now be a good time?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 0,
|
||||
"startTime": 2.7
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,88 @@
|
||||
---
|
||||
id: 67b46920c7cf613d9341c0a0
|
||||
title: Task 92
|
||||
challengeType: 22
|
||||
dashedName: task-92
|
||||
---
|
||||
|
||||
<!-- (audio) Maria: Sure, Jim. I'm eager to hear what you think. How's it looking? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Sure, Jim. I'm BLANK BLANK hear what you think. How's it looking?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`eager`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means excited or ready to do something.
|
||||
|
||||
---
|
||||
|
||||
`to`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This is part of the infinitive form of the verb, used to show purpose or intention.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Eager to` is a phrase used to express a strong desire or excitement to do something. For example:
|
||||
|
||||
`I'm eager to start the new project.` - This means you are excited or looking forward to starting the new project.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Maria",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.5
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.14,
|
||||
"finishTimestamp": 8.84
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Maria",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.7,
|
||||
"dialogue": {
|
||||
"text": "Sure, Jim. I'm eager to hear what you think. How's it looking?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"opacity": 0,
|
||||
"startTime": 4.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,106 @@
|
||||
---
|
||||
id: 67b46f01f60803410bf3cbf3
|
||||
title: Task 93
|
||||
challengeType: 19
|
||||
dashedName: task-93
|
||||
---
|
||||
|
||||
<!-- (audio) Maria: Sure, Jim. I'm eager to hear what you think. How's it looking? -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Maria asking Jim about?
|
||||
|
||||
## --answers--
|
||||
|
||||
The progress or status of the work Jim has been doing.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Maria is asking about the quality of the work, not the progress.
|
||||
|
||||
---
|
||||
|
||||
Jim's plans for the next steps in the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Maria is not asking about future plans.
|
||||
|
||||
---
|
||||
|
||||
How the work she has done is turning out so far.
|
||||
|
||||
---
|
||||
|
||||
Jim's thoughts on a specific problem or issue with the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Maria is asking for Jim's general thoughts on the work, not about a specific issue or problem.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
|
||||
# --explanation--
|
||||
|
||||
Listen for key details that show what Maria wants to know.
|
||||
|
||||
`I'm eager to hear what you think.` – This indicates she is looking for Jim's opinion.
|
||||
|
||||
`How's it looking?` – This suggests she is asking about the overall quality or appearance of the work, not a specific issue or future plans.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Maria",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 0,
|
||||
"z": 1.5
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 6.14,
|
||||
"finishTimestamp": 8.84
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Maria",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"startTime": 1,
|
||||
"finishTime": 3.7,
|
||||
"dialogue": {
|
||||
"text": "Sure, Jim. I'm eager to hear what you think. How's it looking?",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Maria",
|
||||
"opacity": 0,
|
||||
"startTime": 4.2
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,92 @@
|
||||
---
|
||||
id: 67b4701b5498a742481e11a4
|
||||
title: Task 94
|
||||
challengeType: 22
|
||||
dashedName: task-94
|
||||
---
|
||||
|
||||
<!-- (audio) Jim: Overall, I think it's quite user-friendly. The design is clean, and the navigation is straightforward. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and complete the sentence below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`BLANK, I think it's quite BLANK. The design is clean, and the navigation is straightforward.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Overall`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word means considering everything or looking at the whole situation. The first letter is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`user-friendly`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This means easy to use or simple to understand for users. This is a compound word. Remember to use `-`.
|
||||
|
||||
# --explanation--
|
||||
|
||||
`Overall` means considering the entire situation or all the factors. For example:
|
||||
|
||||
`Overall, the app is easy to use.` - This means that when looking at everything, the app is generally good.
|
||||
|
||||
`User-friendly` means that something is easy for people to use, especially for those who may not be familiar with it. For example:
|
||||
|
||||
`The new website is very user-friendly, so even beginners can navigate it easily.` - This means the website is simple to use, with a design that makes it easy for everyone to understand.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 9.18,
|
||||
"finishTimestamp": 14.38
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.2,
|
||||
"dialogue": {
|
||||
"text": "Overall, I think it's quite user-friendly. The design is clean and the navigation is straightforward.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 0,
|
||||
"startTime": 6.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,102 @@
|
||||
---
|
||||
id: 67b475073485eb4552b3f098
|
||||
title: Task 96
|
||||
challengeType: 19
|
||||
dashedName: task-96
|
||||
---
|
||||
|
||||
<!-- (audio) Jim: Overall, I think it's quite user-friendly. The design is clean, and the navigation is straightforward. -->
|
||||
|
||||
# --instructions--
|
||||
|
||||
Listen to the audio and answer the question below.
|
||||
|
||||
# --questions--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Jim's opinion about the app?
|
||||
|
||||
## --answers--
|
||||
|
||||
It needs more features to be complete.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is not saying the app needs more features, but that it is easy to use.
|
||||
|
||||
---
|
||||
|
||||
The app is too complicated for new users.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim is saying that the app is `user-friendly`, meaning it is easy for users to use.
|
||||
|
||||
---
|
||||
|
||||
The app has a confusing layout and difficult navigation.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Jim describes the design as `clean` and the navigation as `straightforward`, meaning the app is easy to navigate.
|
||||
|
||||
---
|
||||
|
||||
The app is easy to use, with a simple design and straightforward navigation.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
|
||||
# --explanation--
|
||||
|
||||
Jim's comment about the app being `user-friendly` and having a clean design and straightforward navigation shows that he thinks the app is easy to use and simple in terms of design and functionality.
|
||||
|
||||
# --scene--
|
||||
|
||||
```json
|
||||
{
|
||||
"setup": {
|
||||
"background": "company1-boardroom.png",
|
||||
"characters": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"position": {
|
||||
"x": 50,
|
||||
"y": 15,
|
||||
"z": 1.2
|
||||
},
|
||||
"opacity": 0
|
||||
}
|
||||
],
|
||||
"audio": {
|
||||
"filename": "B1_10-3.mp3",
|
||||
"startTime": 1,
|
||||
"startTimestamp": 9.18,
|
||||
"finishTimestamp": 14.38
|
||||
}
|
||||
},
|
||||
"commands": [
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 1,
|
||||
"startTime": 0
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"startTime": 1,
|
||||
"finishTime": 6.2,
|
||||
"dialogue": {
|
||||
"text": "Overall, I think it's quite user-friendly. The design is clean and the navigation is straightforward.",
|
||||
"align": "center"
|
||||
}
|
||||
},
|
||||
{
|
||||
"character": "Jim",
|
||||
"opacity": 0,
|
||||
"startTime": 6.3
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user