Skip to content
0:00 / 0:00

#systemsthinking#ai-drivendevelopment#softwareevolution

Software engineering at the tipping point

Google for Developers

2.6M subscribers • 31 videos on Hallway

YouTube
  • Recommended by 2 people: 1 on Lobsters and 1 in engineering communities.
  • Presented by Adam Bender, Google
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

462K views5 months ago2 recommendations

Tools and practiceAI and machine learningAI for codingCode review and teamworkDeveloper productivity

Adam Bender uses systems thinking to analyze the systemic impacts of AI-driven software development on developer ecosystems.

Learn to use systems thinking to understand how developer ecosystems guide the evolution of your software systems. Improve your intuition for the systemic impacts of AI-driven software development and understand how you can better prepare for the exciting changes coming to our industry. Speakers: Adam Bender Watch the Professional Development sessions from Google I/O 2026 → goo.gle/professional-developement-IO26 Subscribe to Google for Developers → goo.gle/developers #GoogleIO Event: Google I/O 2026 Products Mentioned: AI/Machine Learning, Cloud

Why it's here

2 people recommend this

What people say. Recommended for understanding the challenges of rollbacks and release management in the era of AI-driven development.

dunyakirkalion Lobsters • Recommends

Software engineering at the tipping point

u/HarySegarin r/kubernetes • Recommends

On “Image scans come back with a few hundred CVEs a week, how are you deciding which ones are worth fixing first?”

Humm rollbacks are harder than before because of LLM and vibe coding. If you have thousands of mr’s and releases ? Which one are you going to revert to? The following talk is explaining all this way better than me. link to this video