Skip to main content

Programming Is Not the Opposite of Meditation

By

Meditation · Daily Life · Anattā · Integration

Programming Is Not the Opposite of Meditation

On coding, flow, frustration, meditative equipoise, anattā, and why everyday activity is the real training ground.

A programmer asked whether intense knowledge work can seem to move in the opposite direction from meditation: sitting practice may release tension, quiet mental proliferation, and bring a greater sense of presence, while coding can involve sustained conceptual activity and sometimes recreate bodily tension or a feeling that consciousness has become contracted or “stuck in the head.”

Is intensive programming fundamentally at odds with meditation? If sitting practice releases tension and opens a greater sense of presence, what should we make of work that requires prolonged conceptual focus and can sometimes seem to recreate contraction?

Programming itself is not the problem

Soh

I do not think computer programming is in the opposite direction from meditation. If programming is something you have always been interested in, it can be easy to enter a state of flow and become “one” with the activity of programming.

Of course, an ordinary flow state should not automatically be equated with realization or with nondual meditative equipoise. The point is simply that conceptual complexity and focused activity are not, by themselves, incompatible with a less divided mode of functioning.

If, however, you encounter a problem, remain stuck for a long time, cannot resolve it, and suddenly become frustrated, then tension naturally arises. But the same is true of many other jobs and life situations. There can be stress in any kind of work.

The real issue is training. Meditation is not confined to the cushion. The on-cushion practice is the groundwork for bringing realization into everyday life and situations, which then become the true training ground.

And by “meditation” here I do not mean merely relaxation, ordinary mindfulness, or a generalized state of non-grasping. Sitting provides the conditions for releasing fabrication and tension, resting in and actualizing one’s true nature, and entering a nondual equipoise in which mental proliferation and the usual structure of subject, action, and object cease.

Stillness is the groundwork, not the destination

Being at peace in sitting and stillness is just the start—the groundwork. If we cannot be at peace and rest in our true nature, free of fabrication and tension, even while sitting in stillness, then what hopes do we have of integrating that in everyday life?

But meditation in sitting or stillness is only the very beginning. Ultimately, there should be no division between stillness and activity. Whether there is meditation is not defined by the posture of sitting.

If you are in equipoise—where mental proliferation, the sense of subject acting upon object, and the usual subject–action–object structure have ceased—then that is meditation even while you are engaged in activities. Once you become distracted and fall back into an afflictive state of selfing, grasping, tension, and reification, that is post-meditation.

The point is not merely to become peaceful in stillness. The deeper training is to actualize that same freedom from fabrication and selfing amid movement, work, relationships, pressure, problem-solving, and adversity.

Being able to release all tensions and all selfing in every moment, including in difficult circumstances and adversity, requires practice. It also requires deep wisdom and increasing clarity concerning our true nature.

After anattā: complex activity is not itself an obstruction

After the realization of anattā, mental activities—even seemingly complex ones—bodily activities, speech, and everything else in the universe can be naturally integrated as the marvelous activities of presence or Buddha-nature.

None of these are impediments in themselves if the “self” is seen through and released in all moments. Thinking is not the problem. Programming is not the problem. Speech, movement, planning, and responding are not the problem.

The problem is the delusional habit of selfing: tension, the subject–object split, the reification of a self, things, and phenomena, and then relating to experience in an afflicted way through those constructions.

So the issue is not the activity of programming itself. The issue is whether, in the midst of programming, a separate doer, thinker, controller, or experiencer is being reconstituted and contracted around the activity, together with the corresponding reification of people, things, situations, and events as separate objects standing over against that subject and being related to from that divided standpoint.

At the same time, realizing anattā is not an endpoint. Habitual tendencies can still remain after the initial insight. The subtler residues of selfing and inherentness are often exposed only when we actually meet conditions in daily life.

There is the self that arises from conceptual reification, seeing through that with anatta insight is entry point. There is the self that arises in marketplace, in day to day activities, anatta of that is graduation.

— John Tan, 2018

the degree of openess and effortlessness are a matter of wisdom in seeing through... and this seeing through is only actualized in moment to moment engagement. We do not know how much residue is left until we meet conditions

— John Tan

Andre posted another good article today about how the 8 worldly concerns in daily engagements relate to agentless-action, dependent origination and emptiness and all these play their inevitable bits in wearing off our obscurations. As the sutra explained, habitual obscurations are exceedingly subtle like scent left behind a container hence there is no short-cut to liberation -- it’s all step by step and bit by bit erosion of the nuances and subtleness of “inherentness” in one’s ignorance.

— John Tan, “Connecting dots, authenticating DO”

The marketplace is where integration is tested

This is why daily life is not secondary to meditation. Sitting gives us the groundwork, but everyday engagements reveal what has actually been integrated and what remains latent.

Programming can therefore become part of practice rather than something opposed to it. Flow is not the only test. In fact, the more revealing moments may be precisely those in which the code will not work, frustration appears, the body tightens, thought becomes compulsive, and the sense of a pressured doer returns.

Those moments show us where the residue of selfing still operates. They expose what may remain hidden in the relative ease and support of quiet sitting. This is why John Tan emphasizes the “marketplace”: moment-to-moment engagement with actual conditions is where openness and effortlessness are authenticated and where subtler habitual obscurations are worn away.

Meditation is not about preserving a special state available only in stillness. It begins with learning to rest in and actualize our true nature without fabrication, tension, or the subject–action–object structure, and then extends into the whole field of living—thinking, coding, speaking, moving, solving problems, meeting frustration, and responding to conditions without reconstructing the contracted center we call “me.”

So I would not treat programming as something that inherently pulls us away from meditation. Rather, it is one of the many conditions in which practice, insight, and residual tendencies can be tested. The aim is not to escape complex activity, but for stillness and activity to become non-divided, so that realization is actualized in the midst of life itself.

The John Tan passages above are reproduced verbatim. Soh’s comments have been edited for English clarity and organization without removing the original points or reducing their intended meaning.

Comments