Pardon me, if I'm wrong, but doesn't the article argue against its initial argument ("Code less, think more")? In my understanding an incremental "delivery" pl

Pardon me, if I'm wrong, but doesn't the article argue against its initial argument ("Code less, think more")? In my understanding an incremental "delivery" plan, like the one illustrated by the comic involves actually more coding and rewriting of things on its way to the final goal. The author admits this even in "Incremental Delivery can actually take more time to finish the whole thing!". Also, I do not get why the clients smiley 3 in the upper row is so angry about the almost convertible looking like chassis if the requirements changed to convertible and the client's smiley 5 in the bottom row is super happy about the chassis with an added windshield. My key takeaway is: Think more about how to built a useful part of a split-up big project, instead of how to build a big project and increment throughout development. And: don't aim for a starship, if you actually want a glider.