The Prompt-Wait-Evaluate Loop: How AI Kills Flow Without You Noticing
A few months ago, I wrote about finding joy in programming in the age of AI. In the personal discussions I’ve had with fellow developers — both before and after that article — one thing keeps striking me. They just say: yes, that’s exactly how it feels.But a question kept coming up in those conversations: why does it feel this way?
- ▪A few months ago, I wrote about finding joy in programming in the age of AI.
- ▪In the personal discussions I’ve had with fellow developers — both before and after that article — one thing keeps striking me.
- ▪They just say: yes, that’s exactly how it feels.But a question kept coming up in those conversations: why does it feel this way?
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,301 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 | Sandor Dargo’s Blog |
| Canonical URL | https://www.sandordargo.com/blog/2026/07/15/how-ai-kills-flow |
| Publication time | Wed, 15 Jul 2026 06:01:34 +0000 |
| Retrieval time | 2026-07-15T06:53:20.690Z |
| Last seen | 2026-07-15T07:52:40.172Z |
| 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 | nPvHOZn7e34S |
| 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
A few months ago, I wrote about finding joy in programming in the age of AI. In the personal discussions I’ve had with fellow developers — both before and after that article — one thing keeps striking me. Most people don’t argue. They just say: yes, that’s exactly how it feels.But a question kept coming up in those conversations: why does it feel this way? Not in the philosophical sense — I covered that. In the mechanical sense. What is actually happening to our attention when we work with AI coding assistants?I want to explore that topic more deeply, because I think understanding the mechanism matters.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Sandor Dargo’s Blog.
Discussion
0 commentsMore from Sandor Dargo’s Blog
