Making your code public is a good exercise in taking the criticism of others, and learning which type of criticism you can easily discard. My GitHub page is fa

Making your code public is a good exercise in taking the criticism of others, and learning which type of criticism you can easily discard. My GitHub page is far from impressive, it's mainly a collection of project that I think are fun to work on, or things I like to play around with in my spare time. Still, I make half-baked things public because I'm hoping someone will come along and offer feedback. In terms of negative feedback, I refer you to this interview with Rich Hickey. http://www.codequarterly.com/2011/rich-hickey/ http://www.codequarterly.com/2011/rich-hickey/ Here's the section I'm thinking of. Fogus: What would you say to people who claim that Clojure is not a “real Lisp”? Hickey: Life is too short to spend time on such people. So even the creator of a programming language (not trivial to implement!) has to field a fair amount of flak from nay-sayers. So if you're inspired to write something, put it out there. The worst thing that can happen is that someone will offer to help. The people tearing it down are spending their lives criticizing rather than creating.