Never committing and stubbornly committing to your first idea are two sides to the same coin. Both champion binary black/white thinking based on gut feelings, not on running real code. The only way forward is to gather data and learn from it.

The author is very careful to point this out

> Going in the wrong direction will at least often give you information, or provide a base to iterate on.

But I suspect the headline will be misinterpreted as "don't do any critical thinking, just pick your first idea and run with it."

> Should our team build a new feature in an event-driven or synchronous way?

I'm going to be non-commital if I think the feature shouldn't be built at all.