> This isn’t what anyone is suggesting. Did you read the article? > Some engineers think it’s a virtue to remain non-committal in technical discussions.

> This isn’t what anyone is suggesting. Did you read the article? > Some engineers think it’s a virtue to remain non-committal in technical discussions. Should our team build a new feature in an event-driven or synchronous way? Well, it depends: there are many strong technical reasons on each side, so it’s better to keep an open mind and not come down on either side. This strategy is fine when you’re a junior engineer, but at some point you’ll be the person in the room with the most context (or technical skill, or institutional power). At that point, you need to take a position, whether you feel particularly confident or not. That is the very first paragraph of the article. Take up your complaints with the author of the article; not me!