The paradox of AI automation at the workplace
Best case, all of a sudden it becomes "too much", and make them feel like you overstepped, as they realize how they are on a path to automate themselves out of their jobs. Worst case, they agree and start working on implementing it...So in conclusion, who defines where the line is to call something a good business improvement and actively contribute to it, and why do so many people not realize that they are chopping the wood below themselves?
- ▪Best case, all of a sudden it becomes "too much", and make them feel like you overstepped, as they realize how they are on a path to automate themselves out of their jobs.
- ▪Worst case, they agree and start working on implementing it...So in conclusion, who defines where the line is to call something a good business improvement and actively contribute to it, and why do so many people not realize that they are c
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,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 | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=49738100 |
| Publication time | Thu, 17 Sep 2026 08:52:52 +0000 |
| Retrieval time | 2026-09-17T09:13:42.482Z |
| Last seen | 2026-09-17T09:13:42.482Z |
| 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 | aqOV4N4tRqq_ · 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
I find it interesting how people are very ambitious to automate their processes at their companies using new AI tools, but they set the limit of automation on their own terms, and if you try to pass it, you become the cynic or negative one.For example, this guy where I work suggested to use LLMs before 1:1 meetings to scan all the data on them from Google Drive and Slack conversations, so they can be better prepared for the conversation. First this sounds very useful, but if you think about it, it tries to automate a process where humans are involved, and just makes things even more detached and robotic, in a world where we are already obliged to minimize human interactions.But then, lets say you like their idea, and even give feedback: Oh, so what if maybe you just create a video chatbot…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.