The Master and the High-Level Language

There is a stance that runs through the history of technology like a thread: the tool becomes the identity. When that tool is called into question, it feels like an attack on the person themselves.

I. The Assembler Generation

The assembly language programmer of the early decades genuinely knew their computer more deeply than anyone thinking in a high-level language. They knew every bit, every register, every clock cycle. That was no illusion. The mistake was different: believing that this depth was the standard — rather than what could be built with it.

Whoever recognized, at the time, that assembly language had become a dead end — not because they couldn't master it, but because they no longer saw the point — had a different compass. Not the method was their reference, but the goal. The machine was a means, not a sanctuary.

II. The Recurring Pattern

The same pattern repeated itself in the late 1990s. Those who wrote websites in HTML, CSS, and JavaScript by hand understood the medium from the inside. Tools like Dreamweaver promised simplification — but they produced bloated code and a dangerous distance from the actual material. Skepticism was justified. Not out of nostalgia, but out of quality consciousness.

Handwritten code had elegance. It revealed what one truly understood — and what one did not. A visual interface, by contrast, conceals the gaps. It delivers results without understanding. That is a form of comfort one pays for dearly the moment something goes wrong.

And yet: skepticism toward such tools was productive only where it came from understanding — not where it arose from habit. The difference is decisive.

III. The German Tradition of the End in Itself

In Germany there exists a proud tradition that philosophers would call Selbstzweck — mastering something for its own sake. This has produced extraordinary things: precision optics, mechanical engineering, musical instruments of world renown, a craft culture without parallel. This stance generates quality through devotion, not through calculation. It is a cultural strength.

But it has a shadow side: it tends to confuse the tool with the work. When the method is sacred, every new method becomes a threat — not because it is inferior, but because it devalues the mastery one has laboriously acquired. The competence one built up over years loses its rank. That is painful. And from this pain comes rejection, which disguises itself as principle.

One wants to remain a creative free spirit. That sounds noble. But it can also simply mean: not wanting to take the next step.

IV. What Applies Today

Artificial intelligence writes programs without the human typing a single line. For many, this is the ultimate betrayal — the total capitulation to the machine. For others, it is the consistent continuation of the same logic: always take the tool that comes closest to the goal.

What is often overlooked: the competence does not disappear. It shifts. Whoever understands how an HTML program functions can intervene precisely in AI-written code — improving, correcting, refining — with judgment, not with fear. The craft persists, but at another level. The master becomes the corrective.

Open source was once a radical opening: knowledge belongs to everyone, tools belong to everyone. Whoever has truly internalized this philosophy does not draw the line at the next tool — they ask: What opens up through this? What becomes possible that was not possible before?

V. Both / And

The most productive stance is not a choice between old and new, between depth and speed, between understanding and delegation. It is a simultaneity: the understanding of the material is preserved — and becomes a corrective, not a constraint.

The AI delivers the rough structure. The human brings the judgment. Neither blind trust in the tool, nor rejection on principle. This is not a compromise. It is precision at a higher level.

Mastery does not reveal itself in mastering a tool. It reveals itself in knowing when to put it down — and when to pick it up.