From CMS to Harness: How Web Development Changed, 2008-2026
2026-11-15 historydevelopmentaiagentsharnessHow web development changed from 2008 to 2026: CMS sites and FTP, frameworks, no-code, AI chat, vibe-coding and the harness, as I remember it.
TL;DR - Eighteen years of building websites on one page. We started inside a CMS and deployed over FTP, moved into frameworks and pipelines, then to AI in a chat window, then to vibe-coding. Now we build inside a harness: a development environment built around agents, with a developer steering it. Each card below is how I remember the era.
I started writing down how we used to work, and it turned out to be easier to draw than to tell.
-
2008-2013 Inside the CMS
Most sites were a CMS, some ready-made, some our own. Frameworks existed, but they felt slow and heavy for the work we had. The frontend was HTML and jQuery. Deploying meant opening an FTP client and uploading the changed files. Version control was rare: the live site was backed up every night and synced, and that was the history.
PHPCMSjQueryFTPMySQL- 2006: jQuery 1.0. By 2008 it was simply how we wrote JavaScript.
- Other stacks were already here: Rails 1.0 in Dec 2005, Django 1.0 in Sep 2008, Node 0.1 in Jun 2009 and Express 1.0 in Nov 2010.
- 2010: among Eclipse users, Subversion 58.3%, Git 6.8% (Eclipse survey). Git only reached 12.8% a year later.
- 2011-2013: the next era was already here. Symfony 2.0 in Jul 2011, Composer in Mar 2012, AngularJS 1.0 in Jun 2012, then Ansible 1.0, Docker 0.1 and React 0.3 in the spring of 2013. We caught up later.
More on that: why I wrote my own framework as a student, and why I wouldn't now.
-
2014-2017 Frameworks and a pipeline
Real projects moved to a framework like Symfony, with Composer, tests, CI and the first deployment tools. On the frontend AngularJS was the one we reached for. Node showed up on the backend, still rarely in the projects I saw.
SymfonyComposerAngularJSCIDockerNodeMongoDB- 2014: webpack 1.0 (Feb) and Docker 1.0 (Jun), and "it works on my machine" slowly became "ship the machine".
- NoSQL went mainstream. MongoDB, released in Feb 2009, reached 3.0 in Feb 2015 and went public on NASDAQ in Oct 2017. That year Stack Overflow first asked about databases, and MongoDB was already fifth, behind MySQL, SQL Server, SQLite and PostgreSQL (survey).
- 2015: Node.js was used by 13.3% of developers, against PHP 29.7%, Python 23.8% and Ruby 8.0% (Stack Overflow survey).
- 2015: 69.3% of developers used Git, 36.9% SVN, and 9.3% no source control at all (Stack Overflow survey).
For more than ten years this is how we turned a ticket into code by hand.
-
2018-2019 Mature on both ends
Framework-based development became the default on both sides: a framework on the backend, React or Angular on the frontend, and new backend stacks next to PHP.
ReactAngularTypeScriptNodeGoKubernetes- 2016: Angular 2.0 (a rewrite, not an update) and Next.js 1.0. Kubernetes 1.0 had shipped a year before.
- 2018: about 88% of developers on Git. Node.js and Angular were the most used, React was the one people wanted to try (Stack Overflow survey).
- 2019: jQuery was still used by 48.7% of developers, ahead of React (31.3%) and Angular (30.7%) (Stack Overflow survey). The old code doesn't leave.
- Nov 2019: GitHub Actions launches, and CI moves into the repository.
What all that machinery ended up costing: a decade of tools built to save effort.
-
2020-2021 Frameworks everywhere, and no-code
More frameworks, more intense. No-code tools took some of the simple sites, and new projects needed a CMS less often. The legacy ones stayed, and someone had to keep them alive.
ReactSymfonyNo-codeLegacy CMS- 2021: Gartner expected the low-code market to grow 23% to $13.8B, pushed by the pandemic (Gartner).
- Jan 2015: Joomla ran 3.3% of all websites and Drupal 2.0%, second and third after WordPress. By Jan 2022 Shopify, Wix and Squarespace had all passed both (W3Techs).
Where it went from here: why a CMS is now harder and slower than no CMS at all.
-
2022-2024 Autocomplete and a chat window
The start of the AI era, and it was early. The editor suggested the next line, a chat window answered questions, and we pasted the answers in by hand. The framework work went on as before.
CopilotChatGPTCopy-paste- I remembered this as starting in 2024. It started earlier: GitHub Copilot was previewed in Jun 2021 and opened to everyone on Jun 21, 2022.
- Nov 2022: ChatGPT, and everyone outside the industry heard about it too.
Under the hood: what a language model actually does with your prompt.
-
2025 Vibe-coding
The agent wrote the code, and we described what we wanted and took what came back. It felt like magic for a week and like a slot machine after that.
Claude CodeAgentsPrompts- Feb 2, 2025: Andrej Karpathy calls it "vibe coding". By November it was Collins' word of the year.
- Claude Code: research preview on Feb 24, generally available on May 22, 2025.
Read: why vibe-coding didn't work for me, and why you still have to learn to code.
-
2026 The harness
Skills came first, then the harness: development environments built around agents and the way they work. A developer manages and supervises, but far more of the work is automated than ever before.
SkillsHarnessMCPAgents- Oct 16, 2025: Anthropic ships Agent Skills, and on Dec 18 it becomes an open standard.
- Feb 11, 2026: OpenAI publishes "Harness engineering", and the practice gets a name.
The parts: what goes into a harness, a rules file in practice, and the CMS this site runs on, built for agents.
What actually changed
Line the eras up and the thing we build inside keeps changing. In 2008 it was a CMS: it decided where the content lived, what a page could be, and what you could change without breaking it. Then came a framework, then a framework on both ends. Now it's a harness, and the CMS this site runs on has shrunk to an index next to it. The frame never went away, it moved from the product to the way we work.
The unit of work grew along with it. A file you uploaded became a commit, then a pipeline run, then a prompt, and now a plan with a harness to check it. The typing kept moving further away from the person.
What I decide hasn't moved at all. In 2008 I decided which files went up to the server. Now I decide what the agent may build and how we'll both know it works. The FTP client is gone, and the responsibility for what goes live is exactly where it always was.