It’s a leading question, likely political, trying to pose innovation as some sort of universal good when engineers intuitively ask “what” exactly they mean by t

It’s a leading question, likely political, trying to pose innovation as some sort of universal good when engineers intuitively ask “what” exactly they mean by that, as evidenced by this post. Any engineer knows intuitively that the answer when it comes to picking new technologies in your architecture is always: “it depends” but that’s not the point. When it comes to socializing the design, imo, it’s another ideologically motivated waste of time. In order to poke holes you must know the problem well enough to do so, but that’s not what people do on their “sprint planning”. Instead everyone has their own problems, which they must complete by the end of the sprint, or get a ding in their performance review. With no accountability in their estimates, there’s no pressure for accuracy. That’s why tests are better than code reviews.