AI, Make the Website Good
The article argues that the proliferation of AI coding agents is not necessarily leading to higher quality software, despite increased production volume. It suggests that while developer tools have improved, the end-user experience often suffers from reliability issues and poor performance. The author emphasizes that human craftsmanship and a focus on output quality remain more critical than the tools used to generate code.
- ▪AI agents are currently used to plan, write, review, and orchestrate code, but the author questions if this improves the actual user experience.
- ▪Recent anecdotal evidence indicates that software reliability has decreased, with GitHub cited as a recent example of these issues.
- ▪Data from Speedlify shows that AI-generated websites frequently fail Core Web Vitals, Lighthouse performance, and accessibility checks.
- ▪The author asserts that caring about the quality of the final output is more important than the efficiency gains provided by new development tools.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,285 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Zach Leatherman |
| Canonical URL | https://www.zachleat.com/web/ai-websites/ |
| Publication time | Thu, 24 Sep 2026 13:08:50 +0000 |
| Retrieval time | 2026-09-24T13:20:29.813Z |
| Last seen | 2026-09-24T13:20:29.813Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
“AI, make the website good” #11k 388542 September 21, 2026 .iframe--card { margin-block: 15vh; } Millions of Large-Language-Model-generated words have been spilled on craftsmanship in this gilded-age of software development. We now have agents to plan how code will be written, agents to write code, agents to review code, agents to orchestrate and dispatch tasks to other more (or less) capable subagents (these heavily subsidized tokens aren’t going to pay for themselves). I’ve been in this game long enough to recognize tooling improvements from software companies at the bleeding edge of technique and application and it usually goes something like this: “If we make it easier for developers to create software, they will have more bandwidth to produce higher quality software!” I’m always left…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Zach Leatherman.
Discussion
0 commentsMore from Zach Leatherman
