Why engineering teams are about to break
About this lesson
This is something I think is going to fundamentally change as we progress on AI adoption. Our workflows and how our teams work were built at a time when we spent most of our time coding. The average software engineer writes 10 to 15 PRs a month. When that's the case, it's fine for everyone else to do code reviews and run all these processes. But when you start writing 10 times more PRs, we're not ready for that. Our processes, our team composition, everything was built without that assumption in mind. So things are starting to break. A lot of teams are changing their practices to fight that. That's the kind of change I'm starting to see. Full interview on @PeterYangYT!
Original Description
This is something I think is going to fundamentally change as we progress on AI adoption.
Our workflows and how our teams work were built at a time when we spent most of our time coding. The average software engineer writes 10 to 15 PRs a month. When that's the case, it's fine for everyone else to do code reviews and run all these processes.
But when you start writing 10 times more PRs, we're not ready for that. Our processes, our team composition, everything was built without that assumption in mind.
So things are starting to break. A lot of teams are changing their practices to fight that. That's the kind of change I'm starting to see.
Full interview on @PeterYangYT!
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
Related Reads
📰
📰
📰
📰
Build a Claude Skill That Replaces Your $99 Cold-Email Tool
Medium · AI
Decide targets workplaces with enterprise AI rollout through CafeOne
TechCabal
Stop Ruining Your Daytime Shots: Why AI is Replacing Traditional Vintage Camera Apps
Medium · AI
The AI Tool I Built for Myself Ended Up Becoming the Product Clients Asked About the Most
Medium · Programming
🎓
Tutor Explanation
DeepCamp AI