3 ms·

The ideal solution is to be less talk, more action. You can fork a repo in Github and submit a pull request when you're ready. Instead of typing out a long comp

The ideal solution is to be less talk, more action. You can fork a repo in Github and submit a pull request when you're ready. Instead of typing out a long complaint, clone the repo and try and fix it if you can. Then push it back, and you've solved the problem for everyone once it's done. Realistically, though, I think you should avoid putting your code in the public domain until you're ready for the criticism or the feedback. Working in the open right from the start and expecting people to stay hush until you personally announce it is a stupid idea if you're concerned about people spreading the word too soon. You're not going to be able to issue an embargo on your work until a set time. In this respect, why would you even push your code to a public Github repo in the first place if you objectively knew it wasn't ready for public consumption?

leoedin 15y ago
Github offers some pretty good version control stuff that git alone doesn't. There are alternatives (bitbucket offers private repos with similar functionality), but if you like the functionality of github and don't want to pay to keep your project private, then it's really your only option. Fortunately there's so much on github it's probably quite unlikely that anyone's even going to look at your code unless you're already known for doing another project.
billpatrianakos 15y ago
I think there's a big difference between just having a public repo and actually promoting it. It wasn't too long ago that I myself wasn't using version control and decided to learn Git. Someone who's just learning isn't likely to pay for a service like that until they get some experience and understand how to really use it. In the meantime they're putting up half baked projects and little experiments that are awesome to them but worthless to everyone else. Don't you remember being a beginner and thinking you've just done something cool and advanced only to find out later that what you did before was actually pretty mediocre? Now, of you're out there actually promoting something you've made it's a different story. You really shouldn't be bragging if you really feel something isn't quite ready. But then again I come back to my point about criticism. There's constructive criticism and there's overly harsh criticism. You're right,mthere should definitely be more talk and less action but we all know how we are. I've seen it a million times. A really cool project comes along and there's always those smartest-programmers-in-the-room types that have to tear it apart like its garbage instead of offering up some constructive suggestions or actually taking action. It'll probably never stop so the best we can do is try to grow thicker skin as project creators and try to be more constructive and less snarky as critics.

leoedin 15y ago

Github offers some pretty good version control stuff that git alone doesn't. There are alternatives (bitbucket offers private repos with similar functionality), but if you like the functionality of github and don't want to pay to keep your project private, then it's really your only option. Fortunately there's so much on github it's probably quite unlikely that anyone's even going to look at your code unless you're already known for doing another project.

billpatrianakos 15y ago

I think there's a big difference between just having a public repo and actually promoting it. It wasn't too long ago that I myself wasn't using version control and decided to learn Git. Someone who's just learning isn't likely to pay for a service like that until they get some experience and understand how to really use it. In the meantime they're putting up half baked projects and little experiments that are awesome to them but worthless to everyone else. Don't you remember being a beginner and thinking you've just done something cool and advanced only to find out later that what you did before was actually pretty mediocre? Now, of you're out there actually promoting something you've made it's a different story. You really shouldn't be bragging if you really feel something isn't quite ready. But then again I come back to my point about criticism. There's constructive criticism and there's overly harsh criticism. You're right,mthere should definitely be more talk and less action but we all know how we are. I've seen it a million times. A really cool project comes along and there's always those smartest-programmers-in-the-room types that have to tear it apart like its garbage instead of offering up some constructive suggestions or actually taking action. It'll probably never stop so the best we can do is try to grow thicker skin as project creators and try to be more constructive and less snarky as critics.