Week 2: one longer paragraph Β· about 20 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.
What you did, what you expected, what actually happened, and how often.
It saves guessing and gets the bug fixed sooner.
βοΈ -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.
π z and s
s is a hiss with no voice. z is the same, but your throat buzzes.
How. Press π, then say it 3 times. Record yourself on your phone and compare.
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.β