Vol. 9: One Key for One Lock: Why Methods Can't Be Copied, from "On Contradiction"

No.
202
Date
Read
14 min
Words
3,019

At the end of the last post, I left a question: if contradiction is in everything and there all the time, can one set of methods handle them all?

That's not nitpicking. The question hides in something we've all done. You see someone's "tried it myself, it works" method, for losing fat, learning English, managing your time, and you save it first. The calculation in your head is always the same: it worked for them, so it should work for me. But when you actually follow it, same method, not a single step skipped, it just doesn't deliver for you.

When this happens, we usually explain it one of two ways: either we blame our own execution, or we decide the other person was bragging. But the next section of "On Contradiction" gives a third explanation, and most of the time the truth is this third one: the method is fine and you didn't slack off. The lock their key was made for just isn't the same lock as yours.

This section is called "The Particularity of Contradiction," and it's the longest section Mao wrote in the whole essay.

Only Someone Burned by Copying Could Write This Section

I covered the background of "On Contradiction" in the last two posts: 1937, Yan'an, curing the Party's dogmatism. I won't go into it again.

But one thing needs to be said on its own: how exactly the disease of dogmatism broke out.

Those people really only had one key in hand: the successful experience of the Russian Revolution. In Russia, the working class rose up in the big cities, took the central cities first, then spread across the country, and that road worked. So in their view, the Chinese revolution had to go the same way: attack the big cities and fight regular positional warfare the way the books said. The result? City uprisings failed again and again, the base areas built up with so much effort were lost, and the Red Army was forced onto the Long March, having lost almost everything.

Mao's diagnosis wasn't "the Russian experience was wrong." The Russian experience was right in Russia. What was wrong was transplanting it unchanged, because the two countries' contradictions weren't the same contradiction at all. Russia's workers were concentrated in the big cities, and the cities were where the revolutionary forces were strongest. More than 80 percent of China's people were peasants. The strength was in the countryside, and the cities were exactly where the enemy was strongest. The same key, facing two completely different locks.

So in the section on the particularity of contradiction, he states it in the firmest possible terms:

Qualitatively different contradictions can only be resolved by qualitatively different methods.

Each thing is itself and not something else because it contains its own particular contradiction. That particular contradiction determines its nature, and so it also determines that it can only be resolved by a method made to match it. In the original text, he lists a string of examples in one breath:

ContradictionMethod of resolution
Between the proletariat and the bourgeoisieSocialist revolution
Between the great masses of the people and the feudal systemDemocratic revolution
Between the colonies and imperialismNational revolutionary war
Within the Communist PartyCriticism and self-criticism
Between society and natureDeveloping the productive forces

You don't need to memorize what's in this table. Just see its shape: every time the left column changes, the right column changes with it. No method is used twice. Then he quotes a line from Lenin and gives it enormous weight:

The most essential thing in Marxism, the living soul of Marxism, is the concrete analysis of concrete conditions.

Notice the wording. Not "one of the important principles," but "the most essential thing," "the living soul." The phrase we've worn out today, "concrete analysis of concrete problems," comes from here. Worn out or not, its standing in the original is much higher than the casual way we use it.

One Line to Carry with You

Here's this section twisted into one sentence for you to take away:

The first step in solving a problem isn't finding a method. It's pinning down the nature of the contradiction. Get the nature wrong, and the harder you work afterward, the further off you go.

This sentence flips an instinctive order of ours. When we hit a problem, our first reaction is almost always "what do I do?" We reach straight for the toolbox, for someone else's success story, for the method that worked last time. But dialectics asks us to reverse the order: don't ask what to do yet. First ask what kind of problem this is. The kind of lock decides which key. However fast you grab a key, if it doesn't fit the cylinder, it's all wasted.

And for this step of pinning down the nature, Mao specifically names three of the easiest mistakes to make. Subjectivity: not going by the objective facts, forcing your own preconceptions onto things. One-sidedness: seeing only one side of a contradiction and not the other. Superficiality: seeing only what the contradiction looks like on the outside, without feeling for the root inside.

These three words sound abstract right now. Below I'll act them out for you with a few of my own experiences.

In Shanghai, I Treated Every Problem as a Technical Problem

In 2022, fresh out of university, I joined a medical device company as an after-sales service engineer. To put it plainly, the person who goes and fixes equipment when it breaks. A few months in, I was sent to Shanghai on my own.

Here was the situation in Shanghai: one type of equipment existed only in Shanghai in all of China, several hundred units of it. The previous engineer had quit, and I was the only one covering the whole region. And what I knew about this equipment was limited to a few glances at it on the production floor before I left. On busy days I'd run between five or six hospitals and not get back to my place until eight or nine at night. When I ran into something I didn't understand, all I could do was call colleagues back at the company. On the worst days I made a dozen calls. If a message went a minute without a reply, I'd just dial.

During that time I had exactly one thought: fix the machine in front of me. I studied engineering, and that's an engineer's instinct. A problem comes up, you dive in and grind away at the technology until it works.

But after grinding for a few months, I slowly started to sense that something was off.

The first thing that was off was the phone calls. I found that asking questions could be wildly more or less efficient. Sometimes I'd describe a problem for ages and the person couldn't help. Not because they didn't care, but because the problem wasn't in their area at all. Later I wised up. When I got a problem, I didn't rush to ask. I first figured out what kind it was: a circuit issue, a software issue, or an operation issue. Then I went to the person who really knew that kind. The problem was the same. I'd just sorted it first, and it got solved at a completely different speed.

The second thing that was off was repeat repairs. I thought about why the workload in Shanghai was so heavy and found that many machines were fixed, broke again, got fixed again, the same unit acting up over and over. The old way had been to clear the fault in front of you and leave. On the surface it was fixed, but the root of the problem was still inside, and a while later it would pop up in a different form. So I started spending a bit more time each visit to dig out the root and deal with it. Each visit got slower, but the total workload dropped sharply.

What really opened my eyes was the third thing. There was a batch of "chronic problem" units, notorious in the hospitals for being impossible to keep happy. Normal repairs never fixed them for good. By an engineer's logic, if you can't fix it technically, keep grinding at the technology until you do. But after grinding for a while, I stopped and thought: within the realm of technology, this may simply have no solution. So I changed direction, went through the application process, and had those machines replaced with new ones, one by one. The problem disappeared at the root.

That hit me hard at the time. Because "replace it with a new machine" isn't a technical move. It's a management move, a resource move, and yet it solved exactly the problem that technical grinding couldn't. Later I called this lesson "solving problems by changing the realm." Many problems that have no solution in an engineer's realm have one lying right there once you move them into the customer's realm or the company's realm. It works the other way too: what looks like a huge "problem" to an engineer may not count as anything to the customer.

After half a year, I went from running myself ragged every day to having a day or two off a week. At the time I just thought I'd picked up some tricks of the trade. It wasn't until I reread this section of "On Contradiction" that I really matched that experience up: what I learned in those six months wasn't how to fix machines. It was how to pin down the nature of a contradiction. Calling the right person was judging which category a contradiction belonged to. Treating the root cause was telling the surface of a contradiction from its inside. Replacing the machines was admitting that the nature of this contradiction wasn't technical, so the key wasn't technical either. Methods are cheap. Judging the nature is what's valuable. Get the judgment right, and the method is often already there.

These past couple of years, the more I look at Luckin and Starbucks, the more it seems like the same principle blown up a few hundred times. Starbucks's winning template is the "third place," a respectable spot outside home and the office, making money from space and experience. That template has been proven all over the world. By the logic of copying experience, making coffee in China meant copying it. But Luckin didn't copy it. It pinned down the nature of the Chinese market afresh: what Chinese people lacked back then wasn't a place to sit and drink coffee. It was a cheap shot of caffeine you could grab on the way. So it built its shops as little pickup windows, focused on pickup and delivery, and set prices at less than half of Starbucks's. You know what happened next: in store count and sales, it overtook its teacher. Two companies, two locks. The people copying the template saw "the coffee business." The people doing concrete analysis saw "China's coffee contradiction, right here and now."

My Weight Jumped 0.7 kg Overnight, but I Didn't Get Fatter

The second experience is much smaller. It happened this April, but it acts out the mistake of "superficiality" especially cleanly.

I was cutting fat this year, training regularly and eating clean, losing about half a kilogram a week, everything going to plan. One day I went out for a two-hour bike ride. The next morning I weighed 78.4 kg (156.8 jin), almost a kilogram lighter than the day before. Sweating on the bike had shed some water. Normal. But the day after that, I trained as usual and ate clean as usual, and the morning scale read 79.1 kg. Overnight, 0.7 kg back.

The reading on the scale was the surface phenomenon. If you only look at that number, there seems to be just one conclusion: I've gained fat back, the cut has gone wrong. And the next move for many people follows naturally: if I'm fatter, eat less, go harder, starve. Some people around me really do this. My mom does. The moment her weight wobbles, she starts starving herself.

But it felt wrong to me. My diet hadn't changed, my training hadn't changed, the calorie deficit was intact. There was no way I'd grown 0.7 kg of fat overnight. It didn't make sense. So I went back through everything I'd eaten those few days, one item at a time, and sure enough, I found it. A while earlier I'd bought a case of beef balls as a protein source. I liked that they had 16 grams of protein per 100 grams and under 8 grams of fat. Great numbers. But I'd missed one number: sodium, 650 milligrams per 100 grams. A 250-gram bag meant 1,625 milligrams of sodium, and on a cut, my daily sodium limit was only 1,600 to 1,700 milligrams. One bag of beef balls used up the whole day's sodium allowance, and anything else with seasoning put me over. Too much sodium, the body holds water, the weight floats up.

Once I'd found that, the nature of this contradiction flipped: it wasn't a contradiction of fat. It was a contradiction of water. And the solutions to these two contradictions don't share a single word. Fat takes a calorie deficit and time, and you can't rush it. Water means drinking more water, eating a potassium-rich banana, going for a walk, and in one to three days it clears up on its own. Worse, think about it the other way: if you write the prescription for "I got fat" and starve yourself, the sodium is still there, the water retention won't go away, the number on the scale may not even move, and your metabolism takes the hit from starving first. Get the diagnosis wrong and the prescription is backwards. You take the medicine, the illness isn't cured, and you collapse first.

Mao's description of "superficiality" could have been tailor-made for this:

Merely looking from afar and, after glimpsing the rough outline of the contradiction, immediately trying to resolve it. Such a way of doing things is bound to lead to trouble.

Standing on the scale and glancing at the number is "looking from afar." The number is real, but the number isn't the contradiction itself. It's just the tip of the contradiction showing above the water. The same surface phenomenon can hide contradictions of completely different natures underneath. Act before you've felt out the nature, and the prescription you write will most likely be backwards.

The Same Thing, a Different Contradiction Along the Way

Particularity has another layer, more hidden than "different things have different contradictions": the same thing, at different stages, has different contradictions too.

I've written about my fat-loss plateau twice already, so longtime readers will know it. This time let's look at just one new side. Early on I used carb cycling, the weight came off smoothly, and after about five kilograms it stalled. What confused me back then was: the plan hasn't changed, so why have I stopped losing? Put it in the language of this section and it's clear. The early cut and the plateau are two stages of the same process. In the early stage, the contradiction was "is the calorie deficit big enough." By the plateau, my body had adapted, and the contradiction had become "how do I break a new balance." Same thing, but the contradiction was no longer the same contradiction, so the key couldn't be the same key either. This year I have more muscle than last year, so I simply switched to gradually cutting carbs from the start. Not because last year's method was wrong, but because the person using it had moved on to another stage.

Learning AI is the same. In the last post I said it's like a level that never ends: solve one problem and the next steps right up. In this post I can add one more thing: those levels coming one after another aren't just many, they each have a different nature. "Can't use it" is a lock of getting familiar with a tool. Use it more and it opens. "Can't ask" is a lock of expression. You have to learn to state your needs clearly. "Don't understand the concepts" is a lock of understanding. You have to read and build a framework. And coding is a lock of engineering again: workflows, standards, testing, each by the rules of engineering. That the levels never end speaks to the universality of contradiction. That each level has a different key speaks to the particularity of contradiction. Only together do the two sentences show the whole road.

One Key, One Lock

Now we can put these two posts together.

The last post said contradiction is everywhere and always there. You can't hide from it and you can't wait for it to calm down, so there's no need to panic. This post says that among all these contradictions, no two are exactly alike, and each has to be looked at up close and concretely, so you can't be lazy. Universality keeps you from panicking. Particularity keeps you from being lazy. No panic, because contradiction is the normal state. No laziness, because each contradiction only answers to its own key.

But once you really put this method to use, a new trouble will soon come knocking.

After doing concrete analysis, you'll find that one thing never has just one contradiction. Take my six months in Shanghai: the technical contradiction, the contradiction in customer relations, the contradiction in company processes, the contradiction in how I split my own energy, all on the table at once. Losing fat too: calories, sodium, sleep, training intensity, each with its own temper. They're all real, they all deserve concrete analysis, but a person only has so much strength. You can't spread it evenly.

So when a pile of contradictions are in front of you at once, which do you grab first? Which one is the thread that moves everything when you pull it?

That question will wait for the next post.

Licensed under CC BY-NC 4.0. Please credit the author and link to xiluluke.com/en/202

Xiluluke

A dialectical minimalist writing about life, reading and thinking.

Comments

0 / 2000Plain text · Line breaks preserved
Comment as

Loading comments…

    Your browser remembers your name and email once you post.

    Related writing

    WeChat · Xiluluke

    WeChat QR code for Xiluluke

    Scan with WeChat, or long-press to save the image.

    Open original ↗

    Buy me a coffee · Xiluluke

    WeChat reward code for Xiluluke
    WeChat
    Alipay code for Xiluluke
    Alipay

    Scan with WeChat or Alipay, or long-press to save the image.