Building an AI-native engineering org
READ THE ORIGINAL SOURCEOpen original sourcetwitter.com · Opens in a new tabSashank Gondala, CTO of FurtherAI, describes nine months of rebuilding the software shipping process around AI agents. He reports that per-engineer daily merged code changes grew about 5x since January while the revert rate stayed under half a percent. Agents now write nearly all code, AI reviews 99% of changes before humans, and low-risk changes can merge without a person. He argues the new bottleneck is planning and review, and that ownership should shift toward engineers, with managers staying close to the product.
One primary source; other links are context, not independent corroboration.
- Primary sourceHacker News · AI
- Discovery linkHacker News
- Linked in source@Lethain
- Linked in sourceMy reply
- Linked in source@claudeai
- Linked in source@cognition
- Linked in sourcePoirot and Sherlock
- Linked in source@furtheraicom
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Open full article view →- Community discussion+5
- Fetched source page+30
- No editor link review+0
- Community link+0
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Sashank Gondala, CTO of FurtherAI, describes nine months of rebuilding the software shipping process around AI agents. He reports that per-engineer daily merged code changes grew about 5x since January while the revert rate stayed under half a percent. Agents now write nearly all code, AI reviews 99% of changes before humans, and low-risk changes can merge without a person. He argues the new bottleneck is planning and review, and that ownership should shift toward engineers, with managers staying close to the product.
A READER'S EVIDENCE CHECKHow to read this signalSix questions about claims, sources, risks, and open checks
This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →
- 01Who is making each claim?
The claimant and whether each claim was measured or asserted are not recorded in this public brief.
- 02What was actually tested?
Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.
- 03Where are the sources?
Original link: twitter.com. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.
- 04What could mislead?
Source claims not independently checked; these are self-reported internal metrics from one company, and the author does not give definitions or measurement methods for several figures.
- 05What is at risk if wrong?
Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.
- 06What would change the view?
No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.
Key findings from the stored brief
- Merged code changes per engineer per day grew about 5x since January, with revert rate under half a percent.
- AI reviews 99% of changes before a person does, up from 60%, and 91% of changes now include tests, up from 15%.
- Up to a third of changes now merge without a person involved, gated by tests, automated checks, and AI review.
- Planning and review now account for about 70% of feature time, up from 40%, making decision-making the new bottleneck.
Source claims not independently checked; these are self-reported internal metrics from one company, and the author does not give definitions or measurement methods for several figures.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
The account offers a concrete, step-by-step record of how one company restructured shipping around coding agents, including where the bottleneck moved. It suggests org design and decision rights may matter as much as tooling for AI-accelerated teams.
Limits and open questions
Source claims not independently checked; these are self-reported internal metrics from one company, and the author does not give definitions or measurement methods for several figures.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Discussion
Comments are reviewed before publication. Discuss the evidence, not the person.
No published comments yet.
Reader discussion opens with accounts. You can read the original source and published comments now.