The invisible artisan behind the screen
Many people view programming as a purely mathematical discipline or a bureaucratic office job. For Paul Graham, the act of creating software resembles painting on a canvas or literary composition far more than classical civil engineering. A talented programmer begins with a sketch on the screen and refines each layer bit by bit, observing the work's immediate response to every brushstroke of code executed on the computer.
In traditional classrooms, university professors often insist that a project must be planned entirely on paper before a single line is typed. This overly formal view ignores the fact that the best understanding of a problem is born during hands-on construction. Just as a painter adjusts the palette as a figure comes to life, system builders discover solutions in the heat of daily development, testing hypotheses in short cycles of trial and adjustment.
This artisan mindset completely transforms an individual's relationship with machines. Instead of treating technological tools like rigid instruction manuals, a curious professional investigates how the gears operate under the hood, seeking an internal structural elegance that few outsiders notice at first glance.
