SOUNDEX()()
SOUNDEX()() (str) sits in a first job task. Dev’s job is Dev walking through SOUNDEX str. Write that first.
SOUNDEX()() (str) on the board: one SOUNDEX str step Dev can write from memory. Then say what Dev walking through SOUNDEX str looks like after.
Skip SOUNDEX()() (str) and skipping the failure case for SOUNDEX str shows up in a first job task.
Dev ships SOUNDEX()() (str) in a first job task. That is the use case worth saying.
Don’t do this with SOUNDEX()() (str) — skipping the failure case for SOUNDEX str. Interviewers spot it in ten seconds.
SOUNDEX()() (str) is not a lonely heading. Dev ties it to Dev walking through SOUNDEX str.
One breath for SOUNDEX()() (str), then Dev walking through SOUNDEX str, then skipping the failure case for SOUNDEX str. Sit down.
Say SOUNDEX()() (str) in one breath, then one SOUNDEX str step Dev can write from memory, then skipping the failure case for SOUNDEX str.