Live data from Hacker News

Show HN: Show HN

news.ycombinator.com

161–170 of 182 posts

Re: Show HN: Show HN

#161
post #147

Earlier quoted context omitted.

The problem is that people are different. Some people will like the diverse community at HN to scrutinise their work to potentially improve it. Otherwise just want positive reinforcement. You can't really put both sides into the same bucket and decide that everyone should sugarcoat all the time. I love criticising and my projects being criticised as long as there clearly is knowledge or experience behind. What if you…

I don't think anyone is suggesting a lack of honest feedback. I don't like the phrase "constructive criticism" because it's been used into meaningless, but that's basically what's being suggested. Let me try an example instead of a definition. Let's say someone is making a clear architectural misstep: They're trying to use python/django on a project, but their goals really require something like Tornado, and they're…

You can always express your feedback/thoughts without calling other person an idiot/fool etc.

Re: Show HN: Show HN

#162
Just noticed this post. Perhaps this was the worst day for us to ask for feedback (https://news.ycombinator.com/item?id=7989526) for our new service, since there are so many ShowHN posts today? :)

Fully agree with the following.

>"Instead of "you're doing it wrong", suggest alternatives. When someone is learning, help them learn more."

Re: Show HN: Show HN

#163
post #147
post #81

Earlier quoted context omitted.

I agree 100%. In addition, a friendly reminder to us all... When you see a Show HN, assume that whoever created it, perhaps not unlike you, is working to drive his or her dreams into existence. Each post represents a dream, a personal story, a literal piece of their Life. For many of us, perhaps the majority of us, that means grinding at the mine during the day, returning home after perhaps a long commute, spending t…

The problem is that people are different. Some people will like the diverse community at HN to scrutinise their work to potentially improve it. Otherwise just want positive reinforcement. You can't really put both sides into the same bucket and decide that everyone should sugarcoat all the time. I love criticising and my projects being criticised as long as there clearly is knowledge or experience behind. What if you…

I agree. It's important, and tricky, to strike the right balance. We're not calling for sugarcoating. That's why the last guideline says:

  When something isn't good, you needn't pretend that it is. 
I'm not sure it's best to have this as well, though:

  But in that case, consider saying nothing.
... because it slightly implies that criticism isn't welcome. Substantive criticism isn't the problem—gratuitous negativity is. So we may revise this.

Edit: We changed it to:

  When something isn't good, you needn't pretend that it is.
  But don't be gratuitously negative.
In other words, you don't need to sugarcoat, but nastiness is unwelcome.

The key word is "gratuitous". Substantive criticism is neutral and about the work. If it's personal or snarky, that's gratuitous.

Re: Show HN: Show HN

#164

Earlier quoted context omitted.

I don't think anyone is suggesting a lack of honest feedback. I don't like the phrase "constructive criticism" because it's been used into meaningless, but that's basically what's being suggested. Let me try an example instead of a definition. Let's say someone is making a clear architectural misstep: They're trying to use python/django on a project, but their goals really require something like Tornado, and they're…

You can always express your feedback/thoughts without calling other person an idiot/fool etc.

I guess it was oriented more towards people who are more negative saying things like "this sucks and will fail because of X, Y and Z" and not personal things like you said.

Re: Show HN: Show HN

#168
post #163
post #147

Earlier quoted context omitted.

The problem is that people are different. Some people will like the diverse community at HN to scrutinise their work to potentially improve it. Otherwise just want positive reinforcement. You can't really put both sides into the same bucket and decide that everyone should sugarcoat all the time. I love criticising and my projects being criticised as long as there clearly is knowledge or experience behind. What if you…

I agree. It's important, and tricky, to strike the right balance. We're not calling for sugarcoating. That's why the last guideline says: When something isn't good, you needn't pretend that it is. I'm not sure it's best to have this as well, though: But in that case, consider saying nothing. ... because it slightly implies that criticism isn't welcome. Substantive criticism isn't the problem—gratuitous negativity is.…

Those last two sentences might be worth appending to the guideline

Re: Show HN: Show HN

#170
post #156
post #114

I'm actually kind of bothered by this. I was about to release signups for a private beta of my current project, but apparently that no longer fits the formal criteria of "Show HN." Disappointing to say the least.

You cannot show something that cannot be seen? I guess?

Well, it can be seen and it can be used, but just not by everyone yet.

I have no idea where I'll go to do a beta now.

Post reply on HN