The problem is that you come across as the very stereotype of a person who is so focused on arguing about an irrelevant detail that there is no point in having the conversation with it. From my experiences with people on the spectrum, I would bet that you are arguing based on YOUR misunderstanding of the situation. And so your blog post can be summarized as, "Person who is convinced that they are right refuses to admit that they could have been wrong."

Let's take the React checkout example that you gave. Your self-illusion is that you were engaged in holistic thinking. And, in fact, you couldn't even see the whole for the first irrelevant detail that caught your attention. This is the opposite of holistic thinking!

First, it is not your job to make that kind of technology decision. You can offer advice, but it is your manager's job. Your job is to make sure that your manager is well-informed. You failed at that job.

If you believe otherwise, then you're wrong. You probably believe you are better equipped to make that decision than your manager. You may well be right about that. (Though, as a rule, we tend to think that we are smarter than we are, and our managers are stupider than they are. But that is a side point.) But you are still wrong about the important point. Which is that it is still your manager's responsibility to make that decision.

You wanted to frame the entire conversation around, "Does this checkout form have a concrete problem that needs fixing?" Your manager's thinking is going to be about very different looking questions. Such as:

- Will switching to React make hiring and training future developers easier?

- Do my existing programmers have the necessary skills to test this technology out?

- Will this technology choice make future projects faster to develop? (For example, do we get wins from a better toolchain, etc.)

- Will this be an interesting project that helps me keep existing employees motivated?

- Are the other claimed wins in the blog post actually going to work out that way?

Your manager needs to think about these things. You may dismiss them as bullshit, but they are not. Companies live and die on such considerations.

Your manager learned absolutely nothing about these things. Your manager may have come away with the impression that you have no idea if there is a problem with the checkout page. But by misunderstanding your role and responsibility, you failed to carry out your actual responsibility within the team. And wound up so upset about it that you wrote a blog post with a strong undertone of, "Here is the kind of stupid I have to deal with at work."

And that AGAIN puts you in the wrong. It literally takes under a minute to go from your blog to your name to where you work. Any coworker who recognizes the blog now knows you're unhappy. Which poisons your work atmosphere. And if this comes to your manager's attention, your manager has to now deal with the fallout from THAT.

Yes, yes. You consider it bullshit. But it is bullshit that can easily get you fired. For good cause. And the fact that you do this AGAIN puts you in the wrong. And your considering it bullshit DOESN'T STOP YOU FROM BEING WRONG. It just means you won't admit it was a mistake.