The higher the tune, the fewer the voices.
Two thousand three hundred years ago a minister explained to a king why nobody sang along with his favourite tune. The anecdote became an idiom about refinement and its loneliness. It is usually read as a ranking. Read against a weekend of consoles, byte dumps and firewall rules, it turns out to describe something else: two kinds of knowledge, one of which cannot be written down and one of which is worthless until it is.
This essay argues one thing. Refined knowledge and coarse knowledge are not two ranks of the same substance. They are two different substances, and engineering needs both, in a specific order, with a specific handoff. Every failure described below came from having one without the other.
TL;DR — five claims
- ThesisSong Yu's two songs are not a ranking. They are two kinds of knowledge. One is available to whoever is present and cannot be transmitted; the other travels and cannot be acquired without the first.
- FactMuscle produced every decisive fact in these forty-eight hours. A byte dump of a configuration file, a fingerprint comparison, a firewall listing, a screenshot of a console. Not one of them was derivable from the documentation.
- FactMind produced every fix that did not need repeating. A named defect class, four gate tests, one criterion changed from a snapshot to a timestamp comparison. Each removed a category rather than an instance.
- InferenceThe handoff is the whole difficulty. A fact that stays in a terminal is a fact nobody else will ever have. A gate written without the fact is decoration. The loop closed four times in two days and every other attempt dissolved.
- ExcludedThis is not about people or about models. The same hands did both kinds of work, sometimes within an hour. The distinction runs through the work, not through whoever is doing it.
The higher the tune, the fewer the voices
The original anecdote is not a complaint about taste. It is a report about transmission.
In the Warring States period, a certain Song Yu answered a king who had been told complaints about him. He described a singer in the capital. When the man sang the village songs, thousands joined in. When he sang the refined pieces, only a few dozen could follow. Song Yu's conclusion is the line that survived: the higher the tune, the fewer who can sing along.
客有歌於郢中者，其始曰下里巴人，國中屬而和者數千人……其為陽春白雪，國中屬而和者不過數十人。是其曲彌高，其和彌寡。
A guest was singing in the capital. When he began with the village songs, thousands in the city joined and sang along. When he sang the refined pieces, no more than a few dozen could follow. So the higher the tune, the fewer who can sing with it.
Song Yu, Reply to the King of Chu (Warring States period)
Two thousand years of usage turned that into a boast. It is cited by people who want to say their work is too good for its audience. But the sentence is descriptive, not defensive. Song Yu is reporting a property of the material. A refined tune is hard to join because joining it requires something the crowd does not have. Nothing about the crowd's worth is implied, and nothing about the tune's superiority is established. What is established is a gap in transmission.
That gap is the subject of this essay, because it is exactly what happened repeatedly over one weekend of engineering work. There were facts available only to whoever was in the room with a machine. And there were structures that could travel to every future room, but only if somebody wrote them down in a form that could fail loudly. The first kind is the village song. The second is the refined one. Neither is better. They do different jobs, and the work collapses when either one is treated as sufficient.
Coarse knowledge is knowledge tied to a presence: this console, this machine, this hour. It dies with the session unless it is converted. Refined knowledge is knowledge that has been converted into a form which outlives the session: a named category, a test, a criterion. The refined form is not smarter. It is merely portable, and portability is the entire reason to prefer it.
Seven moments, each traced to its artifact
Everything below is checkable. Nothing here is a parable dressed as a case study.
A remote-radio system went from a design document to a live service in two days. Along the way: a host migration, seven releases, four registered instances, and a customer who installed the software and saw a black screen. The work was done by two sessions in parallel, which is described elsewhere; this essay is about the two kinds of knowing that showed up inside it.
| Moment | What settled it | Kind |
|---|---|---|
| A tunnel client rejected its configuration for three hours | Printing the file byte by byte. A backslash inside a quoted string starts an escape, so a Windows path became an invalid Unicode escape | Muscle |
| An entry answered 502 with everything apparently healthy | Comparing the certificate being served against the one on disk. They differed, so the process predated the enrolment | Muscle |
| A port believed blocked by a cloud provider | Listing the host's own firewall rules. The panel was innocent; the machine was not | Muscle |
| A customer's black screen | A screenshot of a console showing four warnings, each naming a default that only existed on the build machine | Muscle |
| Four such defaults, fixed four separate times | Naming the class and writing a test that fails when any writable default lands inside the program directory. It caught a fifth on its first run | Mind |
| A restart indicator that reported the wrong answer in one ordering | Replacing a snapshot comparison with two timestamps: was the file written after this process started | Mind |
| Rebuilds that nobody could receive | Writing down that the upgrade channel compares version strings, so a published number can never be reused | Mind |
Every decisive fact came from muscle. Every fix that did not need repeating came from mind. That is not a coincidence of this particular weekend; it is what the two kinds are for. Presence produces facts. Conversion produces reach. A team that only has one of them will either keep rediscovering the same wall or keep publishing rules nobody can apply.
Got in the hand, answered in the heart, unspoken by the mouth
Zhuangzi had two craftsmen for this. Both are about knowledge that will not survive being written down.
A cook has carved oxen for nineteen years and his knife is still sharp, because he cuts through the gaps rather than through the bone. Asked how, he says the thing that matters is not technique.
臣之所好者道也，進乎技矣。……以神遇而不以目視，官知止而神欲行。
What I care about is the Way, which has advanced past technique. I meet it with the spirit and do not look with the eyes; the senses stop and the spirit moves where it wants.
Zhuangzi, Nourishing the Lord of Life (c. 300 BCE)
The passage is usually read as mysticism. Read as an account of expertise it is precise. The cook no longer runs a procedure. He perceives the structure directly and acts, and he cannot hand that perception to anyone as a list of steps. The nineteen years were not spent accumulating rules; they were spent until the rules stopped being the medium.
Zhuangzi makes the same point more bluntly with a wheelwright, who watches his ruler read and then tells him the books are the dregs of the ancients.
斲輪，徐則甘而不固，疾則苦而不入。不徐不疾，得之於手而應於心，口不能言，有數存焉於其間。
In cutting a wheel, too slow and it is smooth but not firm; too fast and it bites but will not go in. Neither slow nor fast, it is got in the hand and answered in the heart. The mouth cannot speak it. There is a knack in between.
Zhuangzi, The Way of Heaven (c. 300 BCE)
The phrase that matters is the one in the middle. Got in the hand, answered in the heart, and the mouth cannot speak it. That is a description of every diagnostic instinct worth having. Knowing to dump the bytes rather than read the file again. Knowing that a permission error on a log path is not a logging problem. Knowing that a probe which returns nothing means the probe was wrong, not the service.
What it can touch
Contact with reality. Encoding damage, filesystem permissions, antivirus behaviour, a firewall nobody remembered, a resolver cache, a process that survived its parent. None of these are in any document. All of them decide whether the system works.
What it cannot carry
It cannot reach the next person. The byte dump that cracked a three-hour mystery was understood by one observer in one hour, and would have to be redone from scratch by anyone else. Unconverted, it is a private asset with a session lifetime.
Where it slips
Mistaking a proxy signal for contact with reality. An exit code, a log line saying the compile succeeded, a version file written before the build. These feel like measurement and are not. Muscle that stops touching things becomes ceremony.
Not because the knowledge is ineffable in principle, but because it is indexed by situation. The wheelwright's knack is a mapping from felt resistance to adjusted force, and the domain of that mapping is every wheel he will ever cut. Any finite description loses the domain. This is why checklists help and never finish the job: they carry the cases already met, which is exactly the set that no longer requires the knack.
Without the compass and the square, no circle and no square
Portability is not elegance. It is the ability to be in the next room without you.
The wheelwright concludes that books are dregs. He is wrong about books and right about the thing he is contrasting them with. A book cannot carry the knack. But it can carry something the knack never could: a constraint that binds people who were not present.
In these two days that took four forms. A name for a defect class, so that the next instance of it is recognisable rather than novel. A test that fails when the class reappears, which is the only kind of rule that enforces itself. A criterion restated as a comparison of two timestamps, which removed an ordering that had been producing wrong answers. And a sentence about how an upgrade channel decides what to fetch, which changed a release decision that was already half made.
Give it a name
Four bugs were fixed one at a time before anybody said the sentence that covered all four: defaults that only hold on the build machine. The naming did not fix anything. It made the fifth findable, and the fifth was found by a test rather than by a customer.
Give it a gate
A rule in a document is a request. A rule in a test is a fact about what can be merged. The difference is not emphasis; it is whether the constraint can act when nobody is thinking about it, which is to say always.
Give it a criterion
Does this certificate need a restart to take effect. The first answer compared a snapshot taken at import time and gave the wrong result whenever the process started before the file changed. The second answer compares two timestamps and cannot be confused by ordering.
Give it a mechanism
The upgrade channel compares version strings. One sentence, no code, and it stopped a rebuild from being published under a number that had already shipped, which would have made the fix unreachable for exactly the machines that needed it.
The refined song is hard to join not because it is better but because it has been compressed for a different purpose: to survive being carried somewhere else. A gate test is a weekend of debugging compressed into a few assertions. That is why it feels abstract to whoever did not live the weekend, and why their difficulty joining in is not a verdict on them. It is the cost of the compression, and the compression is what makes it usable by anyone at all.
A lamp is lit from a lamp, and the first one burns out
Having both kinds of knowledge is common. Converting one into the other is rare.
The conversion has a direction and a deadline. A fact becomes a gate the same day it is found, or it stops being a fact and becomes an anecdote. Anecdotes are what people tell after an incident; gates are what prevent the next one. The difference between the two is whether anything was written that can fail.
Four times in two days the loop closed. A byte dump became a rule about escaping in configuration files. A certificate fingerprint mismatch became a timestamp comparison. Four build-machine defaults became one test about writable paths. A customer's inability to find an input field became a structural assertion about which panel contains it. Each time, the cost of the lesson dropped from one incident to zero.
More often the loop did not close, and the reasons are worth stating because they are mundane. Time pressure. The belief that a fix is finished when the symptom stops. The assumption that whoever found it will remember it. And a specific modern variant: a session that wrote down three rules for itself, restated them several times, and then violated them fourteen times, because the rules were text and nothing refused to proceed when they were broken.
不以規矩，不能成方圓。
Without the compass and the square, one cannot make a circle or a square.
Mencius, Book of Li Lou, part 1 (c. 300 BCE)
The sentence is usually quoted about discipline in the abstract. Its literal content is more useful: the tool, not the intention, produces the shape. A craftsman who means to make a square and has no square makes something else. A team that means to verify its builds and has no criterion that can refuse a bad one ships them anyway, with the best intentions intact and the artifact wrong.
| Without conversion | With conversion |
|---|---|
| The person who found it can solve it again, faster | Anybody can, including somebody who has never seen the system |
| The lesson survives as long as that person's memory or presence | The lesson survives as long as the test suite runs |
| Repeat incidents cost full diagnosis each time | Repeat incidents are blocked before they ship |
| Quality depends on who is awake | Quality has a floor that does not depend on anyone |
Not for sentimental reasons. The conversion requires the fact still be vivid: which command produced it, what the wrong expectation was, which layer lied. Those details decay within hours, and without them the gate gets written loosely enough that the next instance slips through. Every gate in this system that was written the same day has caught something. The ones written later were decoration.
A high tune is not nobler; few voices is not a loss
The part worth keeping after the weekend is forgotten.
Song Yu's line is often used to comfort someone whose work is not appreciated. That is a misuse, and a costly one, because it converts a statement about transmission into a statement about worth. The higher tune is not better. It is less available. Whether that is a loss depends entirely on whether anybody carried it back down.
Which gives the two rules that survived this weekend, in the order they were learned.
The one for the hands
Do not accept a signal in place of a measurement. Version, timestamp including the year, a hash different from the last one, and then actually run the thing. The village song is only worth singing if it is about the room you are standing in.
The one for the head
Every fact earned the hard way becomes a gate before the day ends. Not a note, not a document, not a plan to be careful. Something that refuses to proceed. The refined tune earns its difficulty only if somebody else can eventually sing it.
The division of labour that appeared over those two days was never planned and was never symmetric. One side wrote the design record, the preventive guards and the judgements about mechanisms. The other lived in bytes, consoles, firewalls and scripts a customer could double-click. Neither was senior to the other, and neither could have produced the outcome alone: the guards would have been speculative without the incidents, and the incidents would have kept recurring without the guards.
What made the system better was not either kind of work. It was the moment, four times, when a fact from a console became a gate in a test suite. Each of those moments removed a category of future failure rather than one instance of it, and each cost about ten minutes more than fixing the bug alone.
The refined song has few singers because it was compressed to travel, and the village song has many because it was never meant to leave the room. Engineering needs both and needs them coupled: the presence that can touch the machine, and the form that can outlive the person who touched it. The higher the tune, the fewer who can join, and the greater the loss if nobody writes it down.