CourseNORIA EnglishHomework 1 · short i ↔ eePDF
HOMEWORK 1short i (ink) /ɪ/ ↔ ee (tree) /iː/

2Sound pairs

2A
Sound pairsFor each word: hear it, then say it. Tap a sentence to hear it. Make ee long, short i short.
Sound 1 · ee (tree) /iː/
Sound 2 · short i (ink) /ɪ/
cheeks
What lovely cheeks.
chicks
What lovely chicks.
peel
This peel's got vitamin C in it.
pill
This pill's got vitamin C in it.
bean
Throw out that bean.
bin
Throw out that bin.
teamwork
The team needs more time.
Tim
Tim needs more time.
featurework
The feature is ready.
fixture
The fixture is ready.
heatwork
Who will take the heat?
hit
Who will take the hit?
2B
Which word?Listen. Tick the word a) or b) that you hear in each sentence.
1a) team b) Tim
2a) bean b) bin
3a) feature b) fixture
4a) heat b) hit
5a) peel b) pill
6a) cheeks b) chicks
2C
Sound-pair wordsListen: Number 1, then five words, one at a time. Write 1 for ee or 2 for short i.
abcde
1 · cheeks / chicks
2 · peel / pill
3 · bean / bin
4 · team / Tim
5 · feature / fixture
6 · heat / hit
2D
Sound-pair sentencesListen to six sentences from 2A. Write the word you hear: the ee word or the short i word.
1 2 3 4 5 6

3Say it

3A
Level 1 · short sentencesListen to each sentence, then say it. Only the bold words are scored, and your best try counts. On paper, say each sentence twice and tick a box each time.
1Read the key.
2Clean the field.
3We need more speed.
4Delete it, please.
5Repeat the demo.
6Keep the screen clean.
7Meet the team at three.
8Pick a ticket.
9Click the link.
10Skip the script.
11Sync it with git.
12Fix the big bug.
13Print the list.
14Limit the input.
15Give it a minute.
3B
Level 2 · both sounds in one sentenceAs in 3A: listen, then say each sentence.
1The field is filled.
2Don't sleep, or the date will slip.
3At peak load, pick a bigger server.
4The new build beat the old one by a bit.
5We saw a dip in deep links.
6Did they steal the key, or is it still here?
7Is this seat free? Can I sit here?
8Run this test, then these tests.
9Who takes the heat if we hit a big bug?
10Eat first, then fix it.
11Does the image fit the screen?
12Each ticket needs a link.
13Please list three issues.
14We beat the limit this week.
15Keep it simple, please.
3C
Level 3 · two pairs, a longer sentenceAs in 3A: listen, then say each sentence.
1Commit the fix, then read the field list again.
2Add a deep link to the billing screen.
3Please delete the six old images before the release.
4The index is clean, but the screen is slow to sync.
5Keep the window visible while you speak in the meeting.
6At peak time, the script skips three fields.
7We need a quick fix for the email field.
8Did the team read the ticket before the meeting?
9Kim will fix the leak in the billing system this week.
10These three tickets are still in the new build.
11We can't reach the server, so the build is still red.
12Delete the key, then give the team a new link.
3D
Level 4 · three sentences in one goAs in 3A: listen, then say each short text in one go.
1The sign-up screen is slow. Every field calls the server when you click it. At peak time, people give up.
2Delete the old keys from the settings. Then commit it. We ship the build next week.
3Is the deep link fixed? Not yet. The script still points to a screen we deleted.
4We need three things this week. Clean the index, fix the billing page, and repeat the tests. Then we can release it.
5Kim picked the ticket on Monday. She fixed the email field in a minute. The team agreed to ship it.
6Please read the feedback before the meeting. The client likes the speed, but the images are still big.

4Read aloud

4A
Read aloudListen, then read it aloud and record it. Make ee long, short i short. Your teacher marks it after you send it.
Why the sign-up form was slow

On Monday morning the sign-up form was slow again. Kim checked the logs and found the problem in a minute: every field in the form called the server when people clicked it. At peak time, that was six thousand calls a minute. The fix was simple. We now read each field once and keep it until the user leaves the page. The team shipped it on Tuesday, and the form is quick again.

4B
Read aloudListen, then read it aloud and record it. Make ee long, short i short. Your teacher marks it after you send it.
A deep link that did nothing

Last week a customer sent us a link from an email. On her phone, the deep link opened the app, but it showed an empty screen. Bill found the reason: the link still pointed to an old screen that we deleted in the last release. He fixed the script that builds the links and added a test for each one. Now every link is checked before we ship a new build.

4C
Read aloudListen, then read it aloud and record it. Make ee long, short i short. Your teacher marks it after you send it.
Our release checklist

Before each release, we ask the same four questions. Is every ticket in this sprint finished? Do these tests pass on Chrome, Safari and a real iPhone? Is the feature visible only to the people who need it? Did we clean the old keys from the settings? If the answer is no, we do not ship. We keep the date, but we release a smaller build.