Day 13: Explaining a Bug

Week 2: one longer paragraph Β· about 20 minutes

Today: Warm up: review your flashcards (2 min) 1 Read2 Spell3 Say4 Words

1. Read 5 minutes

When you report a bug, the reader should be able to see the problem without asking you anything. Write four things. First, what you did: the steps, in order. Second, what you expected to happen. Third, what actually happened, with the exact error message. Fourth, how often it happens: every time, or only sometimes. Add a screenshot if it helps. A clear bug report can save an engineer an hour of guessing, and it gets fixed sooner.

How. Read one sentence. Look up. Say it in your own words. Then go on. Keys: β†’ next, ← back, Esc to show all.

Check yourself

What are the four things to write?

What you did, what you expected, what actually happened, and how often.

Why is a clear bug report useful?

It saves guessing and gets the bug fixed sooner.

2. Spell 5 minutes

✏️ -ful has one l

Full has two l's, but the ending -ful has only one.

Watch out. When you add -ly, you get two l's: carefully, successfully.

Test yourself. The words hide. You hear a word, then type it.

3. Say 5 minutes

πŸ‘„ z and s

s is a hiss with no voice. z is the same, but your throat buzzes.

Words

Hear the difference

How. Press πŸ”Š, then say it 3 times. Record yourself on your phone and compare.

4. New words 5 minutes

Say each word out loud. Then make your own sentence with it.

expect

say: ik-SPEKT

to think something will happen

β€œI expected the test to pass.”

actually

say: AK-choo-uh-lee

in fact, really

β€œIt actually took two days.”

error

say: ER-er

a mistake, often shown by a computer

β€œI got an error on login.”

screenshot

say: SKREEN-shot

a picture of your screen

β€œPlease attach a screenshot.”

guess

say: GES

to give an answer without being sure

β€œDon't guess, check the logs.”

Review today's flashcards