Hacker News new | comments | show | ask | jobs | submit login

> Often times, when I seek feedback on a project, it’s not actually constructive feedback that I want; it’s simply approval. I want a pat on the back and a “job well done.”

I think creative people want and need both. I spent a lot of my free time working on a non-fiction book[1]. I'm really aggressive about soliciting feedback: every page of the book links directly to its issue tracker on github[2].

I love critical, detailed feedback. I want my book to be great, and I can't improve the clarity of my writing without people telling me, "this was confusing" or "this was boring". Bug reports fill me with joy.

At the same time, though, the reason they fill me with joy is because they make the book better. And a big part of the reason I care about making the book better is because it means I get more approval, more email patting me on my back.

I'm fortunate enough to also get positive feedback, comments from people that say nothing more than "You're doing a great job!" That isn't actionable feedback, but if I didn't hear those kinds of comments too, I wouldn't have the motivation for the feedback that is actionable.

    [1]: http://gameprogrammingpatterns.com/
    [2]: https://github.com/munificent/game-programming-patterns/issues

I've found the same thing to be true with my book.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact