Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The best feedback I've gotten is typically tough but fair. Some characteristic elements I appreciate help with:

- Benchmarking (to a peer group)

- Clarity (what does/does not come across)

- Technical (pro-tip: this is how to fix)

Of course, some of the onus is on the submitter on how s/he selects the reviewer. This will be a function of how serious they are, and what their purpose is.

An expert reviewer will typically benchmark you to an attainable but more advanced peer group. A lay-reviewer is usually useful for feedback on clarity, direction, or purpose. If something is truly lacking, a reviewer may ask about the intended goals of the project. This typically segues to a discussion on a sub-section of the work that has some merit (hopefully) . Maybe an idea, concept, example. This is still useful, and the reviewer/s avoid painting the whole thing with a broad brush.

Edit: Just wanted elaborate, re: Benchmarking.

For creative work, typically, an exchange is "This part is strong. This part needs work." And the you are referred to somebody elses work:..."Take a close look at what these guys are doing [list XYZ]". It then falls on the reviewee to follow up. And this is where the real feedback takes place. Where you see just what is expected of you and you get a sense of how hard/easy the next step is. But the act of direction, support, and (hopefully) inspiration is what leads to the success.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: