The website was built at the speed of the conversation

Today, Jaktradioen moved from a loose description of what a podcast website should feel like to a working website with people, upcoming episodes, verified listening links, a media gallery and its own domain.

The first brief was short: make it simple, close to arvidlyngnes.no, but shaped by hunting, food, outdoor life, fire, spices, flavours, trips and dreams.

Roughly two hours later, the site had been built and published through a sequence of small decisions in the same conversation. We added the people one by one, corrected names, gave each person a more human title, connected Spotify and Apple Podcasts, created a gallery, registered the domain and configured its DNS records step by step.

The observed gain was not only faster coding. It was the removal of coordination between the idea and the implementation. The same working context held the purpose, language, design choices and publishing state. A correction did not become a task for later. It became the next version of the site.

The site also stayed deliberately small. It did not need a CMS, a design handoff or a separate launch project. For now, sending a sentence, image or video into the conversation is enough to update it.

What changed: Website creation became a continuous editorial conversation rather than a chain of handoffs.

What I think matters: AI becomes materially useful when it can preserve intent while moving all the way from an unfinished thought to a published surface. The speed came less from generating code quickly than from keeping decisions and execution together.

What remains uncertain: This model works well while the site and media library remain simple. If the archive grows substantially or several people need to publish directly, a more explicit content and upload workflow may become necessary.