How This Website Was Built — Without Writing a Single Line of Code

A real, working website — built, published, and kept running by talking to an AI.

Everything you're looking at right now — the words, the design, the working contact form, even the server this page is running on — was built by one person having a conversation with an AI assistant called Claude. No one on this project wrote code by hand, edited a configuration file, or memorized a programming language. They just described what they wanted, and it happened.

How it actually worked

Describe it

Someone typed, in plain language, what they wanted: a website, then a contact page, then a language switcher, then this very page. No technical terms required.

Claude builds it

The AI wrote the actual website — the pages, the design, the server that runs it — and connected it to a system that watches for changes.

It goes live

Within about a minute of each request, the change was already visible on the real, public website — no separate "deploy" step for a human to remember.

You don't need to know how to code

That's the actual point of this page. Building a website used to mean learning a programming language, understanding servers, and debugging cryptic errors for weeks. Here, the entire job of a human was to describe an idea in normal sentences and look at the result. The AI did the typing, the technical decisions, and the troubleshooting.

When something broke, the AI fixed it — not a person

A few times along the way, something on the server quietly refused to cooperate. Nobody had to become a systems administrator to solve it — the AI simply looked at what went wrong and tried a different approach until it worked:

  • A file needed to be updated but was still "busy" — the AI waited a moment and tried again.
  • A security setting was blocking a change — the AI figured out which one, adjusted it, and moved on.
  • A first attempt at something simply didn't work — the AI read the error, understood it, and quietly fixed it on the next try.

So... where is this all heading?

This is a small example of a much bigger shift. Building software used to require years of training. Increasingly, it requires being able to describe, clearly, what you want — the same way you'd explain it to a capable colleague. That doesn't mean programmers disappear; it means the distance between "I have an idea" and "it exists and works" keeps getting shorter, for more people. The skill that matters more and more isn't typing syntax — it's knowing what you want to build, and being able to say so clearly.

This page — like the rest of the site — was written and published the same way: someone described what they wanted, and Claude did the rest.