How to handle manager adding AI bs to our codebase/designs etc.
Joined the company out of college with like 5-6 years coding hobby projects etc. & started a year ago. I'm basically the highest performer in my team, get more stories & points/higher complexity tasks & have my work done way quicker with virtually no defects etc.etc. Ok fine, there are good & bad uses for AI & if ur atleast checking the code, it's np.
- ▪Joined the company out of college with like 5-6 years coding hobby projects etc. & started a year ago.
- ▪I'm basically the highest performer in my team, get more stories & points/higher complexity tasks & have my work done way quicker with virtually no defects etc.etc.
- ▪Ok fine, there are good & bad uses for AI & if ur atleast checking the code, it's np.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,667 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=49771657 |
| Publication time | Sun, 20 Sep 2026 01:18:04 +0000 |
| Retrieval time | 2026-09-20T01:18:46.203Z |
| Last seen | 2026-09-20T01:18:46.203Z |
| 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 | UNS-DSwf_5Nz · 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
Joined the company out of college with like 5-6 years coding hobby projects etc. & started a year ago. I'm basically the highest performer in my team, get more stories & points/higher complexity tasks & have my work done way quicker with virtually no defects etc.etc. In comparison, most of the team spends like 2/3 the sprint getting their stories deployed & then up until the end of the sprint fixing the defects (usually producing defects that we don't catch until either I have to work in their area or the tester's find it randomly months later in regression)So recently the company's been trying to pump the stock so they asked everyone to go all in on AI dev work. Ok fine, there are good & bad uses for AI & if ur atleast checking the code, it's np.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.