Just listened to this episode. I think we as an industry are missing an opportunity to think about engineering productivity. If we rethink about iterative development, it's very much about idea validation. Not just in the feature shipped, but also in the approach taken. It's why we run spikes in the team. As the cost of code approaches zero it becomes cheaper for us to validate more ideas/options. Ideas in the past that may have been to risky to contemplate, because of the time sink, now become less costly. I think there is a measure of productivity around ideas validated that we're missing. I don't think cycle time encompasses this, as it may be optional scope that ends up getting delivered because we find ways to do it cheaper than if we didn't have AI assistance throughout the team.
Trying to keep it at the team level as UI tools, product definition tools are just as impactful as the Dev tools
Just listened to this episode. I think we as an industry are missing an opportunity to think about engineering productivity. If we rethink about iterative development, it's very much about idea validation. Not just in the feature shipped, but also in the approach taken. It's why we run spikes in the team. As the cost of code approaches zero it becomes cheaper for us to validate more ideas/options. Ideas in the past that may have been to risky to contemplate, because of the time sink, now become less costly. I think there is a measure of productivity around ideas validated that we're missing. I don't think cycle time encompasses this, as it may be optional scope that ends up getting delivered because we find ways to do it cheaper than if we didn't have AI assistance throughout the team.
Trying to keep it at the team level as UI tools, product definition tools are just as impactful as the Dev tools