completely correct, but I dont think thats where OP is coming from or what the article intends to suggest either. Its recommending that you try multiple things, get a feel for whats technically feasible & if it looks interesting to the customer and push that forward. Its very well applicable to indie devs & also applicable to large companies to some extent. This philosophy is great to identify the feature/product you want to spend meaningful time on.
In fact, one could wager that the situation you described is directly a consequence of not adhering to what OP is suggesting.
In fact, one could wager that the situation you described is directly a consequence of not adhering to what OP is suggesting.