4 ms·
> We all write some ugly hacks. Just release it and work on it in public, it's fine. I think we here underestimate the amount of people that assume that the co
by jedimastert 5y ago
> We all write some ugly hacks. Just release it and work on it in public, it's fine.
I think we here underestimate the amount of people that assume that the code found on GH is production ready, or at least people assume the author thinks it's prod. You'll basically have to pre-populate an entire kanban of "yes I'm aware this is broken, don't make another bug about it", and making that digestible for the public may well just take as long as just cleaning everything up.
There really is a level of entitlement you find, often in the form of "I based a project on this thing, now this bug is blocking me, so you are blocking me until you fix this bug you made". And yeah, you can just say "sucks to be you" but is it worth the hassle?
- AshamedCaptain 5y agoWhy do you care about people emailing you at all ? It doesn't matter what you publish or in which state you do it, you will always get a shitton of emails ranging from "but, will this work on my Xbox?" (for a desktop program) to "I see you are expert in $RANDOM_TOPIC, would you kindly help with my homework coding assignment?" If people would email me about "Hey, I couldn't built this on my system because of Y" or the like, I would actually be very happy.
- jedimastert 5y agoSignal-to-noise ratio (I'm talking about bug tracking specifically). If you want to any kind of feedback, you have to take all of it, and if publish in a "rough" state then that noise ratio will be high.
- AshamedCaptain 5y agoMy point is that the feedback will be mostly crap anyway, and actually releasing it in an unusable state (which is far from the truth) would not change that, or may even increase the quality of the feedback as a filter. Why would you even have bug tracking?