Web News: AI vs No-Code
Mike and Matt discuss a growing trend of companies abandoning no-code website builders in favor of agentic AI coding workflows, prompted by an article about a company that tore down their no-code site to return to coded development. They debate the pace and scope of this transition, touching on who benefits most, what happens to established platforms like Webflow and Squarespace, and how AI agents are fundamentally changing the developer workflow.
Summary
The episode centers on an article by Chris McCauley titled 'Why We Tore Down Our No-Code Site and Went Back to Code,' which serves as a jumping-off point for a broader discussion about whether AI-powered agentic coding workflows are replacing traditional no-code tools. Mike opens by arguing that a transition is already underway, where developers and agencies are increasingly using LLM-powered tools to build and iterate on websites faster than WYSIWYG no-code platforms allow, particularly for marketing sites that require rapid A/B testing and content iteration.
Matt provides a grounding counterpoint, noting that many small-to-medium businesses are not choosing their web platform based on technical capability — they often call and request Webflow or WordPress by name because their teams are familiar with those tools. He also highlights that a large portion of his clients barely have time to fill in the blanks of a pre-built CMS, let alone manage an agentic coding workflow. He argues that the 'rambunctious, tech-savvy entrepreneur' demographic is a flashier but smaller slice of the market, and that most small businesses don't care if their footer color hasn't changed in five years.
Mike pushes back by explaining that agentic tools are becoming increasingly end-to-end — handling hosting via partnerships with Vercel and Netlify, compressing and optimizing images automatically, running web vitals checks, and tightening the client feedback loop from weeks to days. He argues that even for agency owners like Matt, the agentic workflow would free up time by automating content research, competitive analysis, and iterative changes, allowing them to serve more clients with less overhead.
The conversation expands into a more philosophical question raised by Matt: if AI agents are writing all the code, why would they use React or Next.js at all instead of compiling directly to vanilla HTML, CSS, and JavaScript — or even lower-level outputs? Mike concedes this is a valid long-term trajectory, suggesting that current framework usage is largely maintained for human readability and review, as well as for the rich ecosystem of pre-built integrations (auth, e-commerce, etc.) that have been developed around these frameworks. He notes that for purely static sites, he's already writing more vanilla HTML than he has in a decade.
Both hosts acknowledge that no-code platforms are aware of the threat and are already reacting — Webflow announced a partnership with OpenAI Sites the day before recording, suggesting that established platforms are trying to integrate agentic capabilities rather than be displaced by them. Mike argues that any company serious about long-term growth will have to adapt, and that the transition among working developers has already happened faster than expected — every developer he's personally spoken to in the last four to six months has moved from writing code to reviewing AI-generated code.
The episode closes with Matt introducing the 'coma test' as a way of gauging whether a change is significant enough to matter — and both agree that the AI shift in web development absolutely passes that test, concluding that anyone waking up from a three-year coma and trying to open a code editor would be completely lost in the new landscape.
About this episode
Are AI coding agents making traditional no-code tools obsolete? In this edition of Web News, Matt and Mike discuss the growing trend of teams moving away from no-code platforms and back toward code-driven websites powered by AI. From Webflow and Squarespace to agentic workflows, rapid iteration, and the future of web development itself, they explore whether AI is changing how websites are built - and whether we’re witnessing the next major shift in the industry.
Key Insights
- Mike argues that every developer he has personally spoken to in the last four to six months has shifted from writing code themselves to reviewing 100% AI-generated code — a transition that happened in months, not years.
- Mike claims that agentic coding tools are becoming end-to-end pipelines that handle hosting, image optimization, web vitals checks, and deployment automatically — making them comparable in ease-of-use to no-code tools while offering far more flexibility.
- Matt argues that the primary reason many businesses use no-code tools like Webflow or WordPress is team familiarity and brand recognition, not technical capability — meaning the marketing engines of these platforms are a major barrier to displacement.
- Mike contends that the biggest beneficiaries of the shift to agentic workflows are not solo entrepreneurs but agency owners, who can tighten client feedback loops from weeks to days and manage more clients with the same headcount.
- Matt raises the point that a large portion of small business clients don't even have the bandwidth to fill in the blanks of a pre-built CMS, suggesting that the added complexity of navigating tokens and hosting in agentic tools could be a barrier for non-technical users.
- Mike observes that Webflow's announced partnership with OpenAI Sites signals that major no-code platforms are already trying to absorb agentic capabilities rather than compete against them, indicating the industry itself sees the writing on the wall.
- Mike and Matt agree that in the long run, AI agents writing code will likely render JavaScript frameworks and even no-code tools obsolete, with output potentially compiling directly to low-level formats — since frameworks were abstractions designed for human readability, not machine generation.
- Mike describes a specific agentic debugging experience where the AI autonomously SSH'd into a production server, tailed multiple system logs simultaneously, cross-referenced them with the codebase, and identified the root cause of a bug — a task he said would have taken him hours to do manually.
Topics
Transcript
All righty, everybody. This is another edition of the web news. Mike put this one together, so he's going to run it for the most part. If you haven't already heard, though, don't look at me and try not to listen to me too much, although I'm going to be in this debate, so that's kind of a crazy thing to say. But I am quite ill, and I look terrible, and I feel not too great, so please excuse the coughing and that, i am on the mend anyway just a little after that little disclaimer there mike why don't you take this web news away absolutely so this one came to me uh like i've been thinking about…
Full transcript available for MurmurCast members
Sign Up to AccessMore from HTML All The Things - Web Development, AI, and Developer Careers
AI Coding Makes Development Easier - So Why Are We Burning Out?
Hosts discuss how AI coding tools, while making development easier, are paradoxically causing burnout by eliminating the struggle-and-satisfaction cycle that previously sustained developer motivation. They explore the psychological toll of AI-assisted work where accomplishment feels hollow and recommend finding personal projects and adjusting workflows to maintain job satisfaction.
Kimi K3 Brings Frontier AI Into the Open
Kimi K3, a new 3 trillion parameter open-source AI model, represents a major advancement in frontier AI that rivals closed-source models like GPT-5.6 and Claude Opus. While offering exciting possibilities for corporations to run powerful AI locally without subscription costs, it poses significant safety risks by allowing malicious actors and state entities to deploy unrestricted AI systems without safety guardrails.
JavaScript Isn't Always the Answer: Native Browser Features Every Developer Should Know
This episode discusses how modern browsers have evolved to handle features that previously required JavaScript or Flash, such as form validation, accordions, dialogs, popovers, and responsive images. The hosts argue for using native browser APIs and semantic HTML instead of over-engineering with JavaScript, which reduces code complexity, improves performance, and enhances accessibility.
Growing Your App: From MVP to MLP
The episode discusses the distinction between MVP (Minimum Viable Product) and MLP (Minimal Lovable Product), using a golf score-tracking app as a case study. The hosts argue that building too many features due to AI-enabled development can complicate products unnecessarily, and emphasize the importance of user feedback, gut instinct, and resilience when determining what features actually make a product worth using.
What Happens When Physical Games Disappear?
The speakers discuss Sony's decision to end physical disc production for PlayStation games by 2028, exploring the cultural impact beyond ownership and preservation concerns. They debate whether eliminating physical media removes an important part of gaming culture that supports both collectors and the broader gaming industry, using an audiophile-to-consumer market analogy.