PCA is an incredibly valuable tool that I've used in most jobs I've had. It's just a terrible idea as a default part of a feature engineering pipeline (which is what the author is talking about in terms of "feature selection"), for reasons outline in this article.
I suggest you don't be quite so quick to dismiss important concepts in this area, and before criticizing this post, at least read through it (I noticed your comment about misunderstand what the author is discussing by "feature selection" is the top comment here).
Nope, never. I'm not dismissing PCA altogether; I'm sharing my experience and pointing out that some topics come up much more often in interviews than on the job.
Just for this convenient use alone I would place them above PCA.
Why not just bootstrap in the regular old non-parametric way? Why inject k-means into it?
Finding good ones can be very problematic. The k-means process is a reasonable method to get good enough starting values without having to think/compute too much.
https://en.wikipedia.org/wiki/Expectation%E2%80%93maximizati...
Personally I never would have guessed that, in retrospect it makes sense... to each their own!