## Document: Tasks Overview ### Overview This image displays a textual document outlining a set of tasks, presented as a hierarchical bulleted list. The document specifies setup requirements, the nature of the primary task, and the format for completing and submitting the tasks. Key information, such as the number of programs to debug, the expected duration, and data collection policy, is highlighted through styling (bolding and blue text). ### Content Structure The document is structured with a main title at the top-left, followed by three primary bullet points, each with several sub-bullet points. * **Title:** "Tasks" (located at the top-left, in a large, bold font). * **Main Bullet Points:** * "Setup:" (positioned below the title, indented). * "Task: Debug five incorrect Python programs" (positioned below "Setup:", indented). * "Task format" (positioned below the "Task: Debug..." section, indented). * **Sub-Bullet Points:** Each main bullet point has nested sub-bullet points, further indented, providing specific details. ### Content Details The document provides the following information: * **Header:** * "Tasks" * **Main Bullet Point 1: Setup:** * "Use a laptop or desktop computer, not a phone" * **Main Bullet Point 2: Task: Debug five incorrect Python programs** * The word "five" is visually emphasized (bolded). * "Each program is an incorrect attempt to solve a coding challenge" * "Your answer should explain what the program is doing wrong" (The phrase "explain what the program is doing wrong" is highlighted in blue text). * "Expect ~10 minutes per task" * **Main Bullet Point 3: Task format** * "Each task is in a separate website" * "Submit your answer using the Google form embedded in each page" * "No other data is being collected" (The phrase "No other data is being collected" is highlighted in blue text). ### Key Observations * The document clearly outlines instructions for a debugging task. * Specific numerical information, such as "five" programs and "~10 minutes per task," is provided. * Important instructions and assurances are highlighted using blue text, specifically regarding the requirement to "explain what the program is doing wrong" and the privacy statement "No other data is being collected." * The use of different bullet point styles (solid circle for main points, hollow circle for sub-points) helps to visually distinguish the hierarchy of information. ### Interpretation This document serves as a concise instruction set for participants undertaking a programming task. The "Setup" section ensures participants have the appropriate computing environment. The "Task" section clearly defines the core activity: debugging five Python programs, each representing a failed attempt at a coding challenge. The emphasis on "explain what the program is doing wrong" suggests that the assessment focuses on diagnostic ability and clear communication of errors, rather than just providing a corrected code. The time estimate of "~10 minutes per task" provides participants with an expectation for the duration of each debugging exercise. Finally, the "Task format" section details the logistical aspects, indicating that tasks are web-based and answers are submitted via an embedded Google form. The explicit statement "No other data is being collected" is a crucial privacy assurance, likely intended to build trust and encourage participation by addressing potential concerns about data privacy. Overall, the document is designed to be clear, informative, and reassuring for participants.