If You Are Asking for Human Attention, Demonstrate Human Effort
The increasing use of AI-generated content in the workplace has raised etiquette questions about when it is acceptable to share this content with teammates. Sharing unedited AI output can be seen as inconsiderate and may lead to fatigue, as humans are already spending a significant amount of time reading AI-generated text. To address this issue, it is essential to demonstrate human effort when requesting human attention, such as reviewing AI-generated code and adding personal commentary to AI-generated content.
- ▪An increasing amount of debug investigations, document writing, and code is being written by robots.
- ▪Sharing unedited AI output can be seen as inconsiderate and may lead to fatigue.
- ▪Demonstrating human effort when requesting human attention is essential in the workplace.
Hacker News (Front Page) files mainly under programming. We currently carry 634 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
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 | Tombedor |
| Canonical URL | https://tombedor.dev/human-attention-and-human-effort/ |
| Publication time | Thu, 11 Jun 2026 23:01:55 +0000 |
| Retrieval time | 2026-06-11T23:25:46.459Z |
| Last seen | 2026-06-11T23:25:46.459Z |
| 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 | JICaGGuME_73 |
| 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
If You are Asking for Human Attention, Demonstrate Human EffortJune 11, 2026 · 2 min readAn ever-increasing volume of debug investigations, document writing, and code is written by robots. This has created a new etiquette question when working with a team - when is it OK to forward the output of an AI to another human to read? On one hand, an AI with robust integration to internal code bases and documentation often produces genuinely1 useful output. On the other, as an increasing amount of a software engineer's day is spent reading AI text, a fatigue sets in. If I can have a robot say something, so can you. It reads as inconsiderate to post un-digested AI output as though it's your own writing. I remember the first time I experienced this annoyance.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Tombedor.
Discussion
0 commentsMore from Tombedor
