You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
17There's a difference between releasing code on a forum and releasing a project with the source available to those who care. Even for large open source projects with many users and potential developers looking at the code, "I think your code has flaws X and Y" type reactions seem to be rare.user7043– user70432011-11-13 21:29:45 +00:00Commented Nov 13, 2011 at 21:29
-
17From the description, the criticism you got that time a few years ago made you a better programmer. So why are you so afraid of criticism this time? Do you feel like you don't need to become a better programmer any more? If you want to get better, you've got to put your ego aside and take a few knocks.Paul Tomblin– Paul Tomblin2011-11-13 22:11:07 +00:00Commented Nov 13, 2011 at 22:11
-
4The cool thing about open sourcing is that, if people complain, you can always just ask them to fix the issues for you.blueberryfields– blueberryfields2011-11-14 00:56:46 +00:00Commented Nov 14, 2011 at 0:56
-
4If you have specific areas of doubt, raise them at codereview.stackexchange.com.pdr– pdr2011-11-14 01:01:51 +00:00Commented Nov 14, 2011 at 1:01
-
12BTW if embarrasement was an issue, we would never had projects like Wordpress or Joomla... More than half the blogs out there are on WP, noone seems to care for the quality of the codebase...yannis– yannis2011-11-14 04:50:52 +00:00Commented Nov 14, 2011 at 4:50
|
Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you