Fresh Reassessment
Attempt after repairing a weak domain, before opening the matching key. There is no speed cutoff. Use documentation for computer operations and lookup tasks; explain numerical reasoning before calculator verification. Demonstrate all tasks in each required domain, rather than compensating for a weak domain with a high score elsewhere.
A. Computer basics
A1. Create reading-practice/logs and save a plain-text day-one.txt inside it. Close and reopen it and verify the extension.
A2. Describe how to locate that file from reading-practice and from logs, and explain why the relative paths differ.
A3. Copy it to day-one-copy.txt, edit only the copy, and demonstrate unchanged original contents.
A4. Identify the editor, browser and terminal on your machine; demonstrate a saved edit visible after reopening the file.
B. Arithmetic and units
B1. Find the total and mean of 12, 18 and 24 minutes.
B2. Express 9 out of 12 as a simplified fraction, decimal and percentage.
B3. Convert 1.25 hours to minutes and divide a 2,800-byte file into complete 400-byte records.
B4. Evaluate 4 + 3 × 5, (4 + 3) × 5 and 2^7 using ordinary mathematical notation.
C. Algebra
C1. Solve 4x + 2 = 26 and verify by substitution.
C2. Evaluate h(n) = 3n + 2 at n = 5 and explain input versus output.
C3. For T(n) = 7 + 4n milliseconds, find T(0) and T(5) and identify fixed and per-item costs.
C4. Solve 4x + 3 ≤ 23; give an allowed and a disallowed value and explain why one example alone is insufficient.
D. Technical reading and help
D1. Interpret “A page count is a whole number from 1 through 500 inclusive. Blank means no entries; empty comma-separated fields are invalid.” Classify 1, 500, 501, 2.5, blank and 12, with reasons.
D2. In the linked shell introduction, use the “Navigating in the shell” section to locate relative versus absolute paths. No new tool installation or full lecture is required; a file-manager check is acceptable. Record the title, URL, paraphrased claim and your own local check using the new practice folder.
D3. Write a sanitized help request for a changed problem: an edit appears in your editor but is absent after reopening the file. Include goal, environment, steps, expected/observed result and a hypothesis you can test. Do not assert that unsaved changes are definitely the cause before checking.
Compare with the key, update the record, and return to the progression rules. If the same task remains weak, use a smaller example or ask for targeted help. Optionally recheck a changed example after a week and record whether it remained independent. This readiness rehearsal is not an extra advancement gate; Programming Basics has separate required delayed checks.