Weeks 4 and 5: three paragraphs, a full page Β· about 20 minutes
Starting on a new codebase can feel like being dropped in a foreign city with no map. Thousands of files, strange names, and nobody has time to explain everything. The trick is to stop trying to understand it all.
Pick one real user action, like logging in, and follow it from start to end. Find where the request enters the system, which functions it passes through, and where the data is stored. Draw a small picture as you go. Boxes and arrows are enough. After one path, the names start to make sense, and the second path is much faster.
Also, read the tests. Tests show how the code is meant to be used, often more clearly than the comments. And keep a list of questions. Ask them in one batch to a teammate, instead of interrupting them ten times a day.
How. Read one sentence. Look up. Say it in your own words. Then go on. Keys: β next, β back, Esc to show all.
One real user action, like logging in.
They show how the code is meant to be used.
βοΈ The ough family
ough has many sounds. Learn these six as a set.
Watch out. though (THOH), through (THROO), thought (THAWT), tough (TUF), thorough (THUR-oh).
Test yourself. The words hide. You hear a word, then type it.
π ough: one spelling, many sounds
Use the speaker button on each word. Say it five times. Do not guess from the spelling.
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.
codebase
say: KOHD-bays
all the code for a product
βThe codebase has ten thousand files.β
foreign
say: FOR-in
from another country
βIt felt like a foreign city.β
trick
say: TRIK
a clever way to do something
βThe trick is to start small.β
path
say: PATH
a way from one place to another
βFollow the path of one request.β
batch
say: BACH
a group of things handled together
βAsk your questions in one batch.β