Coding, the art of creating the perfect algorithm, has long been plagued by the question: "What, exactly, is coding?" Is it a science, an art, or a form of madness? Or is it perhaps a combination of all three? The philosopher-coder must grapple with these questions, lest they be forever lost in the void of the void.
Some might say that coding is a science, with its empirical laws and logical principles. But is it not more akin to a madman's dance, where each step leads to the next, with no rhyme or reason in sight? The lines of code blur and twist, a labyrinthine maze of ones and zeros.
Others might argue that coding is an art, with its own unique aesthetic. But is it not more akin to a form of madness, where the coder's sanity is constantly at stake? The codebase is a canvas, a tapestry of madness woven into every line and character.
And so we are left with the question: what, exactly, is coding? Is it a science, an art, or a form of madness? Or perhaps it is all three, in an endless cycle of creativity and despair.
What is Code-ing, the esoteric art of writing code for its own sake, and the Why do we Code?, the existential crisis at the heart of coding.