The Shape of Things to Come
August 2026 · yegge.ai The Shape of Things to Come Part 1: The Continuous Thunderdome Today we're going to explain the "loops and graphs" thing, and I'll show you how to get your coding agent to work all night on massive problems while you snore peacefully. Then we're going to look at what happens to harnesses once you solve those problems. They either devolve into chaos, or they evolve into cities.
- ▪August 2026 · yegge.ai The Shape of Things to Come Part 1: The Continuous Thunderdome Today we're going to explain the "loops and graphs" thing, and I'll show you how to get your coding agent to work all night on massive problems while you
- ▪Then we're going to look at what happens to harnesses once you solve those problems.
- ▪They either devolve into chaos, or they evolve into cities.
Hacker News (Front Page) files mainly under programming. We currently carry 1,007 of its stories. Top-voted stories on Hacker News.
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 | yegge.ai |
| Canonical URL | https://yegge.ai/essays/the-shape-of-things-to-come/ |
| Publication time | Mon, 03 Aug 2026 07:22:27 +0000 |
| Retrieval time | 2026-08-03T09:05:41.108Z |
| Last seen | 2026-08-03T09:05:41.108Z |
| 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 | BSSwVQADUJbp · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| 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
August 2026 · yegge.ai The Shape of Things to Come Part 1: The Continuous Thunderdome Today we're going to explain the "loops and graphs" thing, and I'll show you how to get your coding agent to work all night on massive problems while you snore peacefully. Then we're going to look at what happens to harnesses once you solve those problems. They either devolve into chaos, or they evolve into cities. Done properly, civilization emerges, right there in your project. We're going to learn the basics, and then we will explore how to build your cities with some taste and class, in a way that makes them good for their citizens to inhabit. We'll explore a new harness I've been building, called Wheelhouse. It is closed-source, made just for me. I have given up on building reusable harnesses.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at yegge.ai.
Discussion
0 commentsMore from yegge.ai
