Code Recurring Ideas

In the last chapter you learned to read a single account closely, staying with the words on the page and noticing what they do and do not say. That skill works one account at a time. But most of the meaning in a set of accounts lives in the ideas that come up again and again, across different people who have never met. This chapter gives you the technique for catching those repeats: coding. Coding is the bridge between reading one account well and seeing the patterns that run through your whole set.

What Is a Code?

A code is a short label you attach to a piece of an account to name the idea that piece expresses. It is not a summary of the sentence, and it is not your opinion about it. It is a handful of words that answer one question: what idea is showing up here?

Suppose someone writes, “I’m forty-one and I still can’t play a full song, but honestly I don’t mind.” You could attach the codepermission to be a beginner. Another person writes, “Half of what I make is lopsided, and I don’t really care.” That is a different sentence about a different hobby, but it carries the same idea, so it gets the same code. Once two accounts share a code, you have found something that recurs, and recurrence is exactly what you are hunting for.

The act of going through your accounts and attaching codes is called coding. As you go, you keep a running list of every code you have used, called a codebook. The codebook matters because it keeps your wording consistent: if you label one linepermission to be a beginnerand a near-identical lineit's ok to be bad, your set will look like it holds two ideas when it really holds one.

How Do You Write a Usable Code?

A usable code is short, names the idea rather than the topic, and could travel across accounts. Compare these:

• Weak code:the guitar. This names the topic, not the idea. Every line about a guitar would get it, and it tells you nothing.

• Weak code:they said they are forty-one and still cannot play a whole song. This just repeats the sentence. It can never match a second account, so it can never show you a pattern.

• Strong code:permission to be a beginner. It names the idea underneath the words, and it could sit next to a line about pottery, singing, or baking just as easily.

Aim for two to four words. Name the idea, not the object it happens to be about.

Underlining marks where something interesting is. A code says what the interesting thing is, in words you can reuse. That difference is what lets you line up ten accounts and see that four of them are quietly saying the same thing.

Code Across Your Set

Coding is a pass across your accounts, not a one-time read. Here is the procedure:

1. Take one account and read it closely, the way you practiced in the previous chapter. Mark the ideas that stand out.

2. For each marked idea, write a short code beside it. Name the idea, not the whole line.

3. Move to the next account. When the same idea appears, reuse the code you already have. When a genuinely new idea appears, add a new code and write it in your codebook.

4. Keep going through every account, reusing codes wherever an idea repeats and adding new ones only when you truly meet something new.

5. When you finish, read down your codebook. The codes that appear across several accounts are your recurring ideas, and they are what you will build on next.

The discipline is in step 3. The goal is not to invent a fresh label for every sentence; it is to reuse a label whenever the same idea comes back. A set where every line has its own unique code has told you nothing, because nothing recurs.

See Coding in Action

Imagine a small study that asked people one question: what does taking up a creative hobby as an adult give you? The accounts below are invented for this course, but they behave like real ones. Watch how the same ideas surface in different words.

Account 1 (guitar):

I’m forty-one and I still can’t get through a whole song without a mistake, but honestly I don’t mind. When I pick up the guitar, an hour vanishes and I haven’t once reached for my phone. That almost never happens in the rest of my life.

Account 2 (painting):

Nobody is ever going to see these paintings, and honestly that’s the only reason I can make them. The second I picture someone standing behind me judging the thing, my hand freezes up.

Account 3 (pottery):

Most of what comes off the wheel is lopsided, and honestly I don’t really care. But I made one bowl last week that actually sits flat, and now I eat my cereal out of it every morning like it’s a little trophy.

Now the coding pass. Each excerpt gets one or more short codes:

Look at what the codebook now shows. The codepermission to be a beginnerappears in two different accounts, about two different hobbies, in completely different words. That repeat is not something you invented; you found it by labeling consistently. Notice, too, that you have only labeled the ideas here. You have not yet decided what they add up to. Grouping these codes into a larger idea is the next chapter’s job, so for now, resist the urge to draw a conclusion. Your task ends when the codes are attached and the repeats are visible.

Your Turn!

Below are three more excerpts from the same study on adult creative hobbies. Code them yourself, by hand, without asking an AI tool to do it for you. The whole point is to train your own eye for recurring ideas, and a tool would hand you labels before you have learned to see them.

Excerpt 1 (baking):

I burned three loaves before one came out right. My family teases me about it, but I genuinely don’t care what they think of the bread. I just like the four hours where I’m not thinking about work.

Excerpt 2 (choir):

I can’t read music and I’m probably the worst one in the room. Nobody has ever made me feel that, though, and I leave every Wednesday about ten years lighter.

Excerpt 3 (writing):

I write a page most mornings that no one will ever read. If I thought someone might, I’d start performing on the page instead of just being honest with myself.

Your deliverable is a small coding table. For each excerpt, quote the phrase you are coding and attach one or two short codes. Reuse a code whenever the same idea comes back, exactly as you would across a real set. Aim for codes of two to four words that name the idea, not the hobby.

Let’s Recap!

• A code is a short label that names the idea a piece of an account expresses.

• Coding means passing across your accounts and attaching codes, reusing a label whenever the same idea returns.

• A usable code is two to four words, names the idea rather than the topic, and could apply across different accounts.

• You keep a codebook so your wording stays consistent and real repeats become visible.

• Coding only labels ideas; deciding what those ideas add up to comes later.

You can now attach reusable labels to the ideas that recur across a set of accounts. In the next chapter, you will take a handful of related codes and group them into a theme, moving from scattered labels to the larger patterns of meaning that a whole set reveals.

Model Solution

Here is one clean coding of the three excerpts. Your exact wording may differ; what matters is that you named the ideas, kept your labels short, and reused a code where the same idea returned.

Notice two things. First,not for an audienceappears in both the baking and the writing excerpt, in different words, so it is a genuine repeat and belongs in your codebook once, not twice. Second,permission to be a beginnerhere matches the same code you would have used in the worked example, which means this idea now recurs across the whole study. If your table quotes the actual phrases, keeps each code short, and reuses a label where an idea comes back, you have done exactly what coding asks. You have not tried to say what it all means yet, and that restraint is correct: naming the ideas is this chapter’s whole job.