Sign up to save your podcasts
Or
Share Ep42: Software Development Teams Must Evolve or Die!
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Ep42: Software Development Teams Must Evolve or Die!
Nine months ago, I asked if engineers were really adopting AI in larger companies. Today, that question is irrelevant. We have moved past chatbots and “vibe coding” into the era of agentic engineering.
In this sequel to Episode 2, I explore how my own identity as a developer is being restructured—from writing syntax to managing autonomous fleets of agents that plan, code, and test on their own. I’m also joined by Tony Nysten and Mirva Laatunen from OpenOcean to discuss why this shift is dismantling traditional organizational silos and changing what it means to be a “software team.”
- (00:00) Intro: A sequel to Episode 2
- (00:37) The death of the traditional developer identity
- (02:00) What is “Agentic Engineering”?
- (03:15) Why the “Product Trio” (PM, Design, Eng) is broken
- (06:41) Dismantling silos and the new organizational blueprint
- (09:50) 5 steps to survival: From flat orgs to “vibe” hiring
- (13:32) Interview: Tony Nysten & Mirva Laatunen (OpenOcean)
- (16:00) The unit economics of AI vs. human labor
- (18:20) How VC roles are being disrupted by AI agents
- (23:04) Outro
Key Takeaways
- The New Developer Identity: Coding is now less about syntax and more about reviewing plans and obsessing over outcomes. If you entered this industry just to write code, the problem has shifted.
- Agentic Workflows: We aren’t just using ChatGPT/Gemini; we are managing agents that argue with each other to plan, code, and test independently.
- Organizational Panic: Traditional structures like microservices and agile teams were built for human limitations. Agents expose the bureaucracy in these old systems.
- Hiring for “Vibe”: As technical barriers lower, the most valuable engineers are those with high creativity, business understanding, and communication skills—not just LeetCode proficiency.
Links & Resources
- Original Article: Why are we building software development teams like it’s 2020?
- Reference: Episode 2: How deeply are engineers adopting AI in larger software teams?
- Reference: Episode 16: MySQL, MariaDB, and AI – A conversation with Kaj Arnö
- Talk: Brandon Sanderson: The hidden cost of AI
- Firm: OpenOcean VC
Cast
- Host and Producer: Duleepa “Dups” Wijayawardhana
- Guests: Tony Nysten & Mirva Laatunen
View all episodes
By Duleepa WijayawardhanaNine months ago, I asked if engineers were really adopting AI in larger companies. Today, that question is irrelevant. We have moved past chatbots and “vibe coding” into the era of agentic engineering.
In this sequel to Episode 2, I explore how my own identity as a developer is being restructured—from writing syntax to managing autonomous fleets of agents that plan, code, and test on their own. I’m also joined by Tony Nysten and Mirva Laatunen from OpenOcean to discuss why this shift is dismantling traditional organizational silos and changing what it means to be a “software team.”
- (00:00) Intro: A sequel to Episode 2
- (00:37) The death of the traditional developer identity
- (02:00) What is “Agentic Engineering”?
- (03:15) Why the “Product Trio” (PM, Design, Eng) is broken
- (06:41) Dismantling silos and the new organizational blueprint
- (09:50) 5 steps to survival: From flat orgs to “vibe” hiring
- (13:32) Interview: Tony Nysten & Mirva Laatunen (OpenOcean)
- (16:00) The unit economics of AI vs. human labor
- (18:20) How VC roles are being disrupted by AI agents
- (23:04) Outro
Key Takeaways
- The New Developer Identity: Coding is now less about syntax and more about reviewing plans and obsessing over outcomes. If you entered this industry just to write code, the problem has shifted.
- Agentic Workflows: We aren’t just using ChatGPT/Gemini; we are managing agents that argue with each other to plan, code, and test independently.
- Organizational Panic: Traditional structures like microservices and agile teams were built for human limitations. Agents expose the bureaucracy in these old systems.
- Hiring for “Vibe”: As technical barriers lower, the most valuable engineers are those with high creativity, business understanding, and communication skills—not just LeetCode proficiency.
Links & Resources
- Original Article: Why are we building software development teams like it’s 2020?
- Reference: Episode 2: How deeply are engineers adopting AI in larger software teams?
- Reference: Episode 16: MySQL, MariaDB, and AI – A conversation with Kaj Arnö
- Talk: Brandon Sanderson: The hidden cost of AI
- Firm: OpenOcean VC
Cast
- Host and Producer: Duleepa “Dups” Wijayawardhana
- Guests: Tony Nysten & Mirva Laatunen