Perhaps related, in software development there is the idea of the "Marimba Phenomenon" as first described in the Joel on Software blog [1], where the author observes that: "PR grows faster than the quality of your code. Result: everybody checks out your code, and it’s not good yet. These people will be permanently convinced that your code is simple and inadequate, even if you improve it drastically later. I call this the Marimba phenomenon."
So, in the arguably creative work of creating new software, you are allowed to ship mediocre software at the start, but you do risk making a bad first impression that may be difficult to recover from.
But on the other hand, if you never ship the software product, your software can become outdated by the time you eventually release it, or you can put it off indefinitely and miss out on growth as a developer. So, there can definitely be a balance between releasing a product too early and making a poor first impression, and waiting excessively to polish a product, to the point where the software becomes no longer relevant or outdated.
So, in the arguably creative work of creating new software, you are allowed to ship mediocre software at the start, but you do risk making a bad first impression that may be difficult to recover from.
But on the other hand, if you never ship the software product, your software can become outdated by the time you eventually release it, or you can put it off indefinitely and miss out on growth as a developer. So, there can definitely be a balance between releasing a product too early and making a poor first impression, and waiting excessively to polish a product, to the point where the software becomes no longer relevant or outdated.
[1] https://www.joelonsoftware.com/2003/06/03/fixing-venture-cap...