[geocar]

> If I make software I can see that if I hacked a giant crap of code together that I would want to clean it up before releasing it to public and save my self the embarrassment knowing I could do it better.

I think hardware is the same way. There's also protocols to fabrication that may be difficult to explain. You have support requests and emails wasting your time.

> "enough positive interest from the community". I don't understand that.

I read it as opposed to negative interest.

> If I make software I can see that if I hacked a giant crap of code together that I would want to clean it up before releasing it to public and save my self the embarrassment knowing I could do it better.

You should not be made to feel ashamed for giving something away for free. You should not even suggest that this should be acceptable. It isn't. People who offer comments on code beyond how to add material functionality (i.e. more inputs), make it faster, or decrease the code size are trash humans. Delete and ignore.

[cdstyh]

>People who offer comments on code beyond how to add material functionality (i.e. more inputs), make it faster, or decrease the code size are trash humans.

I strongly disagree. Making code more maintainable and easy to understand is very important. Enforcing style guides is important

[snovv_crash]

Depends on if other people are gonna work on it too, right? By barging in and telling people their indentation is messy because it's a mix of tabs and spaces which isn't consistent on your IDE, you take away the time they might otherwise spend on doing what they want. It isn't there for you, it's a passion project not a job.