It's my understanding the use of the word "idiot" in this context implies someone who is primarily responsible for a significant amount of rework on anything that bears no real fruit, ui redesigns being one potential example. Pretty sure big companies make those mistakes just as much as small. Though I don't think its fair to call someone an idiot for this reason--I think its very challenging to do well.
Also, they are relatively responsive to developer demands, at least as far as the dashboard is concerned. Not that long ago, if you wanted to export a few seconds of logs, you had to setup a Cloud SQL sink that could suck in gigabytes of logs. Not too helpful if you want to analyze just a few hundred lines. People complained, and now you can export the current view to excel/csv. They've also speeded up load times significantly (it's still not snappy though).
But on the notion that large companies specifically don't have hit or miss design or redesigns: I'd argue there's more than enough evidence to the contrary. And, personally, I find Atlassian products to be a very good example of that.
Note: In this regard, I focus mainly on Don Norman's view on "design", which is largely orthogonal to aesthetics. It's cool for software to look nice. But if it's laid out in a non-intuitive way or doesn't prevent (or even provokes) user errors, it's not good design, period.
But yes, you're right, happens all the time. Less so with most of the large scale more popular redesigns people tend to think of when writing articles like this about tools they actually use; the team at Atlassian, for example, is not made of idiots, neither at Slack, Google, Twitter, or other large companies with mostly significant design experience.
Smaller operations where we all likely work—yep, hit or miss.