Code and Words, and Value

The basic unit of literature is the word. A poet stays up through the night, discarding hundreds of words to find that single, perfectly fitting one that will complete a poem. A novelist weaves a narrative that moves the reader's heart, carefully calibrating the rhythm between one sentence and the next. So what of code, the basic unit of programming? A developer tests and discards countless lines of code to find the precise logic that will bring an app to life. Just as words become sentences, and sentences become paragraphs that form a work of literature, code accumulates to become apps and websites. The process bears a striking resemblance to literature. Just as randomly stringing words together does not make literature, listing functioning code does not make great software. Choice and exclusion, structure and flow, and the intent woven throughout — if these are what transform literature into art, then the world of code, shaped by the same principles, belongs equally to the realm of art.

Some fifty years ago, when I was in high school, Korean schools were divided into the humanities track and the science track. Philosophy departments were for humanities students; computer science was for those in the sciences. I chose the humanities track and went on to major in philosophy at university. Back then, that division felt entirely natural. Yet looking back now, how arbitrary that boundary seems. If literature and coding share the same essential starting point, then the wall dividing the humanities from engineering was never a natural order of things — it was an artificial partition drawn by an educational system. Have we not been cutting ourselves off from possibilities beyond that line, simply by accepting it as an inevitable boundary?

Taoist philosophy fundamentally questions binary thinking. Laozi said: being and non-being give rise to each other, and difficulty and ease complement each other. What appears to be opposition is, in truth, a relationship of mutual presupposition and completion. The divisions between humanities and sciences, between art and technology, between the liberal arts and engineering, are no different. These are not opposing forces — they are branches that grew from a single trunk of human inquiry. When we recognize that shared root, the separated branches naturally begin to reach toward one another. What is called the age of convergence today may not be a passing trend, but rather the process of things that were artificially divided finding their way back to where they belong. The era of digging deep into a single well is drawing to a close; the age has come for those who connect many wells and discover new currents beneath the surface.

And yet convergence itself cannot be the goal. A more important question remains: convergence for what purpose? The French thinker Jacques Attali once posed this question to Korean readers: "Am I a person of value?" His answer was that a life which transcends self-interest and contributes to others and to the world is what truly makes a person valuable. This question applies in full to everyone who creates. Whether one writes or codes, the act of making something inevitably brings one face to face with the question: for whom is this creation? The moment a creator puts their work out into the world, they have already stepped into a relationship with others. A creation that turns away from that relationship remains mere technique; a creation that embraces it becomes something of value.

Beautiful sentences and precise algorithms must ultimately be directed toward people. Like a novel that stirs a reader's heart, like an app that makes someone's life a little easier and eases their loneliness — whether the hand that works is gathering words or refining code, the place that hand must ultimately reach is the world and the people in it. Whatever the tool, the value of creation has always resided there.