What happens to engineers when AI writes all the code?
What happens to engineers when AI writes all the code?Engineers aren’t going away. They'll be piloting the product loop.Ian VanagasSep 14, 20264023ShareWe are plausibly coming to a moment where AI will write all the code. This is a reality for many developers already.
- ▪What happens to engineers when AI writes all the code?Engineers aren’t going away.
- ▪They'll be piloting the product loop.Ian VanagasSep 14, 20264023ShareWe are plausibly coming to a moment where AI will write all the code.
- ▪This is a reality for many developers already.
2 outlets in our directory ran this story, first to last over 6 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ DDD matters more when AI writes your code — Three Dots Labs
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,037 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 | Hacker News (AI / LLM) |
| Canonical URL | https://newsletter.posthog.com/p/if-ai-writes-all-the-code-whats-left |
| Publication time | Tue, 15 Sep 2026 16:51:02 +0000 |
| Retrieval time | 2026-09-15T16:56:52.845Z |
| Last seen | 2026-09-15T16:56:52.845Z |
| 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 | J3xLh8N-O1XJ · 2 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
What happens to engineers when AI writes all the code?Engineers aren’t going away. They'll be piloting the product loop.Ian VanagasSep 14, 20264023ShareWe are plausibly coming to a moment where AI will write all the code. This is a reality for many developers already. Over the last 4 months at PostHog, we moved from around 20% of our monorepo PRs being opened by agents to 70%.This breaks the definition of engineer as “someone who writes code.” But no one thinks engineers will go extinct as soon as this happens. Anthropic has claimed “coding is largely solved,” yet it has 208 open roles with “engineer” in the title.So what will engineers be doing?1.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).
Discussion
0 commentsMore from Hacker News (AI / LLM)
