3 ms·

>You point out one example where it's somewhat separate and I can point out many where it's not. That's great. You SAID "zero". And you pointed out zero exampl

>You point out one example where it's somewhat separate and I can point out many where it's not. That's great. You SAID "zero". And you pointed out zero examples to defend your statement. I pointed out one example that completely invalidates your statement, which is all that is needed. Because 1>0. Here, let me help. "Your application doesn't do a good job of separating business logic and presentation." Was that hard? I didn't say anything hyperbolic, I didn't recommend downvotes or call his application "WTF" in that statement. It WAS NOT HARD. >I can also point out numerous massive security flaws, utterly unused code, the obviously unprepared .DS_Store shit, and code which attempts to load missing libraries and SQL inserts when it's blatantly billed as "no database required" Did you do that, or did you try and insult the author? I see others in this thread pointing out specific issues that will help the author. You can't do that? Or is the author not worthy of your help, but somehow IS worthy of the time you spent to insult the author's project? >I'd also argue every single one of my criticisms is incredible valid and hardly hyperbolic. Sorry, but if you say "zero" and it's not true, that's hyperbole. It's either hyperbole or it's not, there's no such thing as "hardly hyperbolic." You exaggerated and you knew it was an exaggeration, OR you thought you were making a true statement. Either way, wrong. http://dictionary.reference.com/browse/hyperbole http://dictionary.reference.com/browse/hyperbole My point is you are not offering anyone anything. Who do you help by insulting the author? The author? Or do you think you're protecting the world from bad software? BTW, here's the rule I think you're violating: >When disagreeing, please reply to the argument instead of calling names. E.g. "That is an idiotic thing to say; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3." One could argue I'm breaking the same rule in arguing with you, though...

aikah 12y ago
Sorry but I have to agree with meritt here. This a SHOW HN, and the project is not ready at all. Even if one disegards bad architecture,the project suffers from too many security flaws. The creators should have a look at http://www.phptherightway.com/ http://www.phptherightway.com/ which is really basic guidelines for any modern PHP project. PHP suffers from bad rep because of developpers that clearly dont know what they are doing. They have client-side skills for sure. But i would feel totally embarassed if someone linked to something i've made and that would look like the source code. I'm not saying i'm a PHP "rockstar". But there are channels where beginners can get code reviews for free (IRC,reddit,...) before making a project official. They need to find a proper developper
- mfisher87 12y ago
  I'm not going to continue arguing this aside from to say that my point has been missed, completely. Maybe this will illustrate my point, but I'm kind of repeating the same stuff: 0th, the rules for Show HNs disagree with both of you. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html First, what is the threshold for making a "Show HN" and getting constructive feedback instead of being told your project belongs in Daily WTF? Specifically, how many security flaws are necessary before insulting an author? The way I see it, this community was intended to be constructive, not destructive. Second, what are Show HNs for? Learning, or circle-jerking? Third, are you saying that "proper developer" is a way one is born? Like... this guy could NEVER EVER learn the facts he needs to improve his software because he is not a "proper developer", so he needs someone else? That's some bullshit. This isn't exactly a complicated application and this elitist attitude is completely unwarranted. I have NO IDEA why I need to say this to anyone on HN. My normal experience on HN is far superior to the crap one might find on reddit, so this is very disappointing... EDIT: I looked up the rules for Show HNs. You think a Show HN is supposed to be a completed product. Here are the guidelines. Emphasis mine >Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread. >A Show HN needn't be complicated or look slick. HN users are comfortable with work that's at an early stage. Seems spot on, except the description of "HN Users" being comfortable with early-stage work. >If your work isn't ready for people to try out yet, please don't put "Show HN" in the title. Once it's ready, come back and share it then. This is subjective. You think it's not ready to try, but the author does. If you disagree, the proper response is to define why it's not ready and help, not to insult the person. WHY are people actually defending destructive criticism here? Pertinently, here are the guidelines for COMMENTS to Show HNs. >Be respectful. Anyone sharing work is making a contribution, however modest. >Ask questions out of curiosity. Don't cross-examine. >Instead of "you're doing it wrong", suggest alternatives. When someone is learning, help them learn more. >When something isn't good, you needn't pretend that it is. But don't be gratuitously negative. Do you see any rules being broken here? I see ALL of the comment rules being broken. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html I think it's possible to acknowledge shortcomings and be constructive at the same time. This commenter agrees, and managed to do what commenters in this thread failed to do. https://news.ycombinator.com/item?id=8132658 https://news.ycombinator.com/item?id=8132658

aikah 12y ago

Sorry but I have to agree with meritt here. This a SHOW HN, and the project is not ready at all. Even if one disegards bad architecture,the project suffers from too many security flaws. The creators should have a look at http://www.phptherightway.com/ http://www.phptherightway.com/ which is really basic guidelines for any modern PHP project. PHP suffers from bad rep because of developpers that clearly dont know what they are doing. They have client-side skills for sure. But i would feel totally embarassed if someone linked to something i've made and that would look like the source code. I'm not saying i'm a PHP "rockstar". But there are channels where beginners can get code reviews for free (IRC,reddit,...) before making a project official. They need to find a proper developper

mfisher87 12y ago
I'm not going to continue arguing this aside from to say that my point has been missed, completely. Maybe this will illustrate my point, but I'm kind of repeating the same stuff: 0th, the rules for Show HNs disagree with both of you. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html First, what is the threshold for making a "Show HN" and getting constructive feedback instead of being told your project belongs in Daily WTF? Specifically, how many security flaws are necessary before insulting an author? The way I see it, this community was intended to be constructive, not destructive. Second, what are Show HNs for? Learning, or circle-jerking? Third, are you saying that "proper developer" is a way one is born? Like... this guy could NEVER EVER learn the facts he needs to improve his software because he is not a "proper developer", so he needs someone else? That's some bullshit. This isn't exactly a complicated application and this elitist attitude is completely unwarranted. I have NO IDEA why I need to say this to anyone on HN. My normal experience on HN is far superior to the crap one might find on reddit, so this is very disappointing... EDIT: I looked up the rules for Show HNs. You think a Show HN is supposed to be a completed product. Here are the guidelines. Emphasis mine >Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread. >A Show HN needn't be complicated or look slick. HN users are comfortable with work that's at an early stage. Seems spot on, except the description of "HN Users" being comfortable with early-stage work. >If your work isn't ready for people to try out yet, please don't put "Show HN" in the title. Once it's ready, come back and share it then. This is subjective. You think it's not ready to try, but the author does. If you disagree, the proper response is to define why it's not ready and help, not to insult the person. WHY are people actually defending destructive criticism here? Pertinently, here are the guidelines for COMMENTS to Show HNs. >Be respectful. Anyone sharing work is making a contribution, however modest. >Ask questions out of curiosity. Don't cross-examine. >Instead of "you're doing it wrong", suggest alternatives. When someone is learning, help them learn more. >When something isn't good, you needn't pretend that it is. But don't be gratuitously negative. Do you see any rules being broken here? I see ALL of the comment rules being broken. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html I think it's possible to acknowledge shortcomings and be constructive at the same time. This commenter agrees, and managed to do what commenters in this thread failed to do. https://news.ycombinator.com/item?id=8132658 https://news.ycombinator.com/item?id=8132658