Ben Stolovitz, a research engineer at Salesforce AI Research, published a post in October 2026 detailing his shift from manual coding to managing AI agents.reported
The claim
He describes a process where each agent receives a separate Git worktree to execute tasks independently. The agents write code, run tests, and create pull requests without direct line-by-line input from him. He claims this setup allows for rapid prototyping, with new features built in approximately twenty minutes.
The response
The post acknowledges that this approach is purely personal opinion and speculation. Stolovitz notes that he previously worked on Microsoft’s Windows AI team and now supports scientists at Salesforce. He admits that norms for using these tools are still forming and that humans are currently "messing up" as AI integrates into daily life. He expresses openness to his current methods being incorrect.
The practical upstop
The material leaves the broader industry impact unverified, focusing solely on one engineer’s experience. Stolovitz emphasizes that he still uses AI in similar ways to the previous year, but with increased automation. He highlights the need for a personal policy to navigate the blurring lines between human and machine output, citing examples of colleagues using AI for Slack messages.
Claims versus evidence
The source is a single individual’s blog post, not an independent audit or company report. Stolovitz explicitly labels his account as "purely my opinion & speculation." The claim that manual coding is "obsolete" applies only to his specific role as a research engineer building rapid prototypes, not to all software development. The $3,000 cost is self-reported and may not reflect average enterprise spending.reported No external validation of the twenty-minute prototype time is provided.
Why it matters
- Product teams may face pressure to adopt similar agentic workflows, impacting hiring and training strategies.
- The reported $3,000 monthly token cost highlights potential budget shifts from headcount to compute expenses.
- The lack of established norms for AI use suggests teams need to draft internal policies quickly.
- Claims of obsolescence in manual coding require careful verification before redefining engineering roles.
Topics: AI agents, coding tools, Salesforce, workflow, token costs
Updated
Then / now / next
Manual coding with autocomplete tools like GitHub Copilot was the primary workflow.
A Salesforce engineer manages multiple AI agents to write and test code autonomously.
Teams may need to develop personal or organizational policies for agentic AI use.
Story timeline
- Then Manual coding with autocomplete tools like GitHub Copilot was the primary workflow.
- 03 Nov 2026 How I use AI (Oct 2026)
- Now A Salesforce engineer manages multiple AI agents to write and test code autonomously.
- Next Teams may need to develop personal or organizational policies for agentic AI use.
The strongest doubt
Counterpoint from the sources
Stolovitz admits his methods are speculative and that societal norms for AI use are still undefined.
For readers
Developers
- Manual coding may be replaced by agent management in some roles.
- Expect rapid prototyping times of around twenty minutes.
Business
- Token costs can reach $3,000 monthly per engineer.
- Teams may need to draft AI usage policies soon.
Researchers
- Agentic workflows support rapid prototype building.
- Current norms for AI integration are still forming.
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.Questions readers ask
How much does the Salesforce engineer spend on AI monthly?
according to the published report, spending approximately $3,000 per month on tokens.
Does he still write code manually?
He states that he no longer writes much code, calling manual coding obsolete.
Connected stories
Reading receipt
- The author spends approximately $3,000 per month on AI token usage.
- He states that agentic coding has made manual code writing obsolete.
