Scope creep is scary when you have the wrong pretext: to "just" implement a small feature or a project, when in reality the prerequisites to do so are enormous.

As usual it's not so black and white and is all about balance.

Project where the sole user is you in your kitchen? Sure, hack it together.

Project where you actually want other people to use the product? A research phase matters and helps here.

Consider what the goal is and the amount of effort to invest typically becomes more evident.

Just code using c++ (or in a language with a similar syntax complexity or a massive runtime, java, microsoft rust, etc). It gets even better with ISO regular feature creep: you'll find always a dev to manage to make hard dependent on the latest "standard".

Basically, you will end up dependent on the massive complexity of a compiler due to the syntax complexity, and the cherry on top, thanks to ISO, you'll get feature creep creating a cycle of planned obsolescence around 5 to 10 years.

Oh, sorry, "they" called that "innovation".

Scope creep is scary when you have the wrong pretext.

[dead]

[dead]

[dead]

[dead]

[dead]