Longer dev cycles gave management time to think through and correct bad business decisions. Now they'll get to tighten that feedback loop where bad decisions (or good ones) get implemented quickly. It will be interesting to see what that split is and the reaction to that.
replyI think it'll also expose how much of that lag time was important to getting everyone's ducks in a row. It's never just add a button, it's also updating the document service and the downstream systems to all accept that new button's input. There's a blast radius and it takes a while for the shockwave to cross to every team that needs to know about it.
replyI dunno. It definitely can happen.
replyCode was never the bottleneck.
I've worked with plenty of teams that did the "in prod the same day" trick without AI.
The problem was just fucking ego. Designer has an ego, product owner has an ego, QA has an ego, stakeholder has an ego, platform teams have massive egos, developers have egos.
Unrelated but: the only reason people are shipping more with AI is because more people are ok with slop now.