> Code that matters is code that's used by other people. For me personally > the ability to share my code with others is the thing that makes > programming worth doing in the first place.
This is a rather important point. One of the most asked questions (random made up fact) by newcomers to a language is "what can I code? what open source programs can I help?". All with the aims of getting better acquainted with the language itself and, hopefully, helping others. I normally direct people to Advice to Aimless, Excited Programmers (http://prog21.dadgum.com/80.html). For those who'd rather read the rest of this email, the tl;dr version is: got scratch your own itch, you might be building an itch-scratcher for others. The real question now becomes (at least for me): how do you know when an itch is worth scratching? how do you know it's a shared itch? I've seen more experienced programmers immediately recognise what'd be useful at large and what wouldn't (when I presented them with a couple "itches" of my own.) Interestingly enough, my judgement didn't necessarily coincide with theirs. Code to scratch your own itch? Sure, that's great. Code to scratch a shared itch? Even better. But how do you know which is which? U -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
