Skip To Main Content
Arjun Iyer on Muck Rack

Arjun Iyer

As seen in: Nature, Entrepreneur, Entrepreneur Europe, heart, Mint, Product Hunt, BioRxiv, DZone, Physical Review B, Public Health On Call and
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Arjun

Contact Arjun, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

Per-developer environments were the goal. Agents moved the goalposts.

|
By Arjun Iyer
| The New Stack Verified
Multi-tenancy has moved in one direction for 60 years: the tenant keeps getting smaller. Mainframe time-sharing carved a single machine into slices so an organization’s departments could share it, and the tenant was the org. Virtualization gave each team its own fleet of virtual machines, and the tenant became the team. Containers and Kubernetes namespaces shrank it again, until a platform team could hand every developer an isolated environment on a shared cluster.
Open in Who Shared Issue with article?

Anthropic recommends a git worktree per agent. Your runtime infra makes that a problem.

|
By Arjun Iyer
| The New Stack Verified
Anthropic recommends a git worktree per agent. Your runtime infra makes that a problem. sponsor-signadot,sponsored-post-contributed, A developer supervising four coding agents has four changes in flight at once, each in its own git worktree. That isn’t an exotic setup anymore: Anthropic’s documentation now treats a worktree per session as the default way to run agents in parallel, and what was an expert workflow two years ago is the recommended starting point today.
Open in Who Shared Issue with article?

How routing keys isolate Kafka consumer tests on a shared broker

|
By Arjun Iyer
| The New Stack Verified
A change to a service that consumes from Kafka is not validated until it has run against the real system: real partitions, real consumer groups, the events other teams produce. Coding agents sharpen the requirement. An agent iterating on a consumer needs to publish an event, observe what its change did downstream, read the failure and rerun, many times per change and in parallel with every other agent’s loops. That only works if a realistic environment is available on demand, for every change.
Open in Who Shared Issue with article?
See all 74 licensed articles (78 Total)