Key points
- Neil Kakkar wrote for The Pragmatic Engineer about his productivity changes at Tano.
- This change occurred after he joined the AI-native startup eight months ago.
Neil Kakkar reported in The Pragmatic Engineer that his code integration volume surged after joining the AI-native startup Tano eight months ago.reported
Evidence: reported
A software engineer details how he went from merging eight to 20 pull requests per month to 200+ after joining AI-native creator startup Tano eight months ago (Neil Kakkar/The Pragmatic Engineer)aifleet-techmeme
What was released or claimed
Kakkar detailed a shift from merging eight to 20 pull requests per month to handling more than 200 monthly.reported
Evidence: reported
A software engineer details how he went from merging eight to 20 pull requests per month to 200+ after joining AI-native creator startup Tano eight months ago (Neil Kakkar/The Pragmatic Engineer)aifleet-techmeme
Who it affects
This account reflects the experience of a single software engineer working within an AI-native creator startup environment.
What is still unknown
The source material does not specify which AI tools or processes drove this productivity increase, nor does it provide data on code quality or error rates.
The practical upshot
The report highlights a potential shift in developer workflow efficiency when operating within companies built around artificial intelligence integration.
What the rules require
Product teams should view this as a single anecdotal report from The Pragmatic Engineer. The material does not establish industry standards or mandatory compliance rules. There are no stated regulations requiring developers to merge 200 pull requests.reported Teams must verify such productivity gains independently, as the source provides no methodological details or benchmarking data to replicate the outcome at scale.
Evidence: reported
A software engineer details how he went from merging eight to 20 pull requests per month to 200+ after joining AI-native creator startup Tano eight months ago (Neil Kakkar/The Pragmatic Engineer)aifleet-techmeme
Why it matters
- Product teams may see peer-reported productivity spikes in AI-native environments, though causality is not proven.
- The lack of tooling details limits the ability to replicate or audit the reported workflow changes.
- Single-engineer anecdotes do not confirm sustainable scaling strategies for larger engineering organizations.
- Readers must distinguish between individual experience and verifiable organizational performance metrics.
Topics: software engineering, productivity, AI startups, developer tools
Updated
Then / now / next
The engineer merged eight to 20 pull requests monthly at his previous role.
He merges over 200 pull requests monthly at the AI-native startup Tano.
It remains unclear if other engineers at Tano or similar startups experience comparable volume increases.
Story timeline
- Then The engineer merged eight to 20 pull requests monthly at his previous role.
- 04 Nov 2026 A software engineer details how he went from merging eight to 20 pull requests per month to 200+ after joining AI-native creator startup Tano eight months ago (Neil Kakkar/The Pragmatic Engineer)
- Now He merges over 200 pull requests monthly at the AI-native startup Tano.
- Next It remains unclear if other engineers at Tano or similar startups experience comparable volume increases.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Terms in this story
pull requests
A method used in software development to propose changes to a code repository.
AI-native startup
A company built around artificial intelligence technologies from its inception.
The Pragmatic Engineer
A publication where Neil Kakkar shared his professional experience.
Questions readers ask
How many pull requests did the engineer merge before joining Tano?
He merged between eight and 20 pull requests per month previously.
How many pull requests does he merge now?
He merges more than 200 pull requests per month.
Where was this information published?
The details appeared in a report by The Pragmatic Engineer.
Reading receipt
- Neil Kakkar wrote for The Pragmatic Engineer about his productivity changes at Tano.
- This change occurred after he joined the AI-native startup eight months ago.
Still open: Which specific tools or methods enabled this productivity increase?
Still open: Does this volume correlate with maintainable code quality?