# Explorer coding: what changed in v1.1.0, sgit.ai > The changes to the article "Explorer coding" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [Explorer coding](../../explorer-coding.md) / [Versions](../explorer-coding.md) / v1.1.0 # Explorer coding: what changed in v1.1.0 From v1.0.0 (2026-10-16, `25f7ed3c9`) to v1.1.0 (2026-10-18, `de821285d`), paragraph by paragraph. 0 paragraphs added, 0 removed, 1 changed in place, 36 unchanged. About 0 words added and 1 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../explorer-coding.md) 1 unchanged paragraph Summary: I would like to propose a better name for what is usually called vibe coding: explorer coding. Vibe coding sounds as if people are just typing and ad-libbing, and I have never liked it, because what they are doing is the best thing to happen to software since the spreadsheet: everyone with a need can now explore it by building, with the fast feedback loop that made spreadsheets win, and what they build is theabestbetter brief anyonethanwillanyever write.document. Explorer is Simon Wardley's word for exactly that kind of work. It also makes the limit clear. An explorer-coded app may look and feel like an application, but nobody has read the code or checked the architecture, and it is not ready to be in line: once other people depend on it, it is mission critical, and it needs villagers to maintain it, with agent behaviour policies, data handling and releases that do not break it, and then town planners who own the code in production and are accountable for it, as the Linux kernel, Fedora and GitHub already say the human who ships code must be. The further towards commodity, the fewer agents in line and the more deterministic code. And it suggests a commercial model: every product should have an explorer version, where users reshape it by talking to it, and paid conversions from there to a villager product and a town planner one. 35 unchanged paragraphs, under In short {#in-short}, Why not vibe coding {#name}, The best thing since the spreadsheet {#spreadsheet}… [all versions](../explorer-coding.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/explorer-coding/v1.1.0.html)*