A new senior joined the team. On their first day, they wrote nothing.
A junior asked, “When will you start contributing?”
The senior replied, “I have been contributing all morning.”
“How?”
“By not adding to what is already too much.”
Beyond the Surface
There is a quiet assumption in most engineering cultures that presence equals output, and that a new hire proves their worth through commits. This koan challenges that assumption directly.
The senior developer’s silence on their first day is not idleness. It is observation. Before adding a single line, they are learning the shape of the system, the habits of the team, and the weight of what already exists. Restraint, in this sense, is itself a form of contribution. Many codebases do not suffer from too little code. They suffer from too much of it, layered without full understanding, each addition making the next developer’s job a little harder.
The junior’s question, “when will you start contributing,” reflects a common but limited view of value. It assumes that only visible output counts. The senior’s answer reframes the entire premise: sometimes the most valuable act is choosing not to add complexity that isn’t needed yet.
For a developer’s own practice, this koan is an invitation to pause before every new function, every new abstraction, every new dependency, and ask a simple question. Does this need to exist? A codebase, like a mind, benefits as much from what is left out as from what is put in.