"If you're not embarrassed by your app then you've waited too long to release it" - Chris Kowalczyk, https://blog.kowalczyk.info/article/2f72237a4230410a888acbfce3dc0864/lessons-learned-from-15-years-of-sumatrapdf-an-open-source-windows-app.html
3 years ago · 👍 martin, bacardi55, defunct
(continued II) All releasing early does is exactly that, ensuring that you have to break backwards compatibility a lot. Users really dislike that. Like there are instances of people getting hate mail over having changed the hue of their icons. · 3 years ago
(continued) There seems to be a massive divide between mature projects that move on a glacial pace, never break, and always work (like the linux kernel, vim, gcc); and the immature projects that just pile code onto github and barely compiles on a good day. Everything is always broken and nobody gives a fuck because they've been told that that moving fast and breaking their users' workflows with every patch is somehow an acceptable practice. · 3 years ago
I disagree with the author on several points. You can absolutely release software too early. There's already far too many half-baked projects out there, and the open source world is especially guilty of this (closed source is far from innocent either). There is no point in rushing something to the market in open source, since there isn't a singular cent to be earned from being first. · 3 years ago
"If you're not embarrassed by your app then you've waited too long to release it"
↑ Fully agree with this, I'm never happy with my code anyway. An
And I love the "release early, release often" idea that aligns with it :) · 3 years ago
Also, "My soul has a price and AdSense can no longer afford it." · 3 years ago
Ah, he adds "I didn't come up with this nugget of wisdom but I agree with it. ". I'll give him credit anyway. · 3 years ago