Our team was refactoring the codebase to follow ML pipeline best practices, but not enough attention had been paid to problem/task formulation, label quality etc.
Less than five years ago, this term was used to describe what my team was doing. The criticism was correct, and my team did change its ways.
At the time, I was unaware of this term, and the explanation given to me was the "misunderstood" one, as explained in the article.
Since that incident, I, too, have pointed out patterns of "cargo culting" as/when I identified them. Not too many, but definitely more than a couple. More than once, I've repeated the same explanation. I've even used the "misunderstood" explanation as a fun anecdote to share at gatherings (both work, and social).
While I don't think less of the original person for referring to my team as a cargo cult (they were sincere in their criticism), the article will definitely stop me from using the misunderstood version of events as the "true" origin of the term. It will change the way I speak about it, even if I refer to this term in the future.