I’m not here to score points. I’m expressing my thoughts and reservations about the article. I’m not even taking much of a position on what developers should do. It’s more of an exploration of the landscape.

Unfortunately, skipping past a legitimate point doesn’t address the point which remains unresolved. It’s a nice rhetorical trick though. I’d rather discuss the point. (Even though others have had discussions, that doesn’t help me understand and learn.) There’s no urgency for me to reach a conclusion, so a bit of rehashing of “tired” perspectives isn’t offensive to me.

Reasonable doesn’t always mean appropriate or best for the situation. It doesn’t always lead to good or better outcomes. Shutting down and dismissing legitimate concerns is not a good way to build a consensus and and will often lead to adverse outcomes. It is ironic that this person’s approach is making the same mistakes they are trying to warn against.

There’s a clear conflict that literally can’t be ignored. It must be considered by all participants, else those participants will be unexpectedly unsatisfied with the outcomes.