Ask HN: How did your boss's behavior change with the rise of AI?
Employees report that some managers increasingly rely on AI-generated code and analysis, often passing unfinished work to others. The AI outputs, including code reviews, bug analyses, and presentation materials, are frequently incomplete or misdirected, creating additional effort for staff. The reliance on AI-generated “recipes” replaces deterministic tools, leading to unpredictable results and increased workload.
- ▪Managers frequently produce AI-generated code snippets that are only partially functional and then delegate the completion to team members, adding extra work.
- ▪AI-driven bug analyses and code reviews often identify issues in non‑production utilities, generating many tickets that require manual triage.
- ▪AI-generated presentations and “recipes” replace stable scripts or tools, but they tend to be inconsistent and require additional time to adapt.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,262 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=49132161 |
| Publication time | Sat, 01 Aug 2026 07:58:13 +0000 |
| Retrieval time | 2026-08-01T08:15:39.805Z |
| Last seen | 2026-08-01T08:15:39.805Z |
| 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 | 5gknjEPNVn7v · 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
Not 100% boss-specific, but...* regularly generating AI-slop code changes that nearly work, and then trying to hand over to someone else for "completion". this is often a pretty terrible experience, and more work than just having a single person take ownershiop of the _outcome_ - i.e. understand the need, write the code, test it, deliver, make sure it works... generally the coding was never the hard part, and its harder to start with broken code than just from scratch.* sporadically sharing AI analysis of bugs/problems/crashes/troubleshooting type stuff. again, often nearly correct... but sometimes more work finding the incorrect aspect than starting from scratch.* lots of AI flavored text and presentations.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.