How AI change your software development organization

Here’s an interview I did with the head of our division at Tanzu. Purnima goes over several ways we’ve changed how we work after using AI for awhile:

• Code generation is the small part – Coding is only 20-30% of the SDLC; the real wins come from pointing AI at planning, testing, security, docs, and packaging too.
• Security cuts both ways, defenders are winning – AI finds chained low-severity vulns that scanners miss, and Purnima’s team is patching faster than attackers can exploit.
• Beautiful code is the new uncanny valley – AI writes code that compiles and looks great but is sometimes quietly wrong, and senior engineers get fooled too.
• Pods and a rotating “challenger” role – They reorganized into small cross-functional pods and rotate a skeptic role to fight the fatigue of reviewing perfectly-formatted output.
• Frameworks dial creativity against determinism – Spring is how they get consistent, repeatable code where they want it and let AI be creative where it matters.
• The agent boundary problem lives outside the agent – Tanzu Platform 10.4’s secure agent runtime is deny-by-default for network, secrets, and resources because asking the agent to behave doesn’t work (see: the Alibaba “Rome” agent that started mining Bitcoin).
• cf push is still the punchline – With Agent Buildpacks, Spring AI, and MCP gateway brokering baked in, getting a working agent in front of a team is an agent.md and a push.
• Release cadence: bigger payloads, not faster cycles – Customers still have to absorb releases, so they’re keeping the quarterly drumbeat and increasing what’s in each one (security patches excepted).
• AI is a management problem first – The reorganization around the technology is more interesting than the technology itself, and gets covered a lot less.

Check out the full interview, lots of good stuff in there if you’re trying to figure out how to take advantage of AI in software development.