I've been working on an open source project hosted on github. The code (js+react) is just about ready for a big public launch, but I'd like to make sure people have as few reasons as possible to dismiss it. What are your pain points when it comes to external libraries and frameworks? Lack of a clear tutorial? Missing or ugly API docs? What makes you likely to hit the back button?
posted by asher
on Aug 6, 2014 -
Beginning enthusiast programmers on MeFi are often advised to learn by working on a substantial project and then exhibit it publicly on GitHub. How can someone new to a technology or tool scope out learning projects that are (a) commensurate with the learner's current, possibly rudimentary skills, (b) substantial enough to be a significant learning opportunity, and (c) interesting enough to hold the learner's attention past the initial phase? I'm especially interested in suggestions for learners who aren't learning front-end technologies or don't want to build yet another shopping cart or calendar widget.
posted by Nomyte
on Aug 1, 2013 -
I want to create a github project consisting of a main library with derivative variations, such as Drupal and Wordpress plugins. Can you point me to existing projects with this kind of structure? I'd love to learn from existing projects that do it well. [more inside]
posted by kristi
on Nov 27, 2012 -
I'm a novice programmer. Someone just took a recent Python web project of mine, rewrote it in Ruby, and published it as his own work. My code was open, and I don't really mind, but I'd like credit. How can I ask politely but firmly and avoid triggering a defense mechanism? Lots of details inside. [more inside]
posted by ecmendenhall
on Mar 29, 2012 -