Hacker News new | ask | show | jobs
by program_whiz 2566 days ago
Basically all the comments here are just critiques. My 2 cents: excellent work, its extremely hard to stick with something for 3 years, especially with people's constant criticism and worries it isn't "big enough". The attitude of the developer seems quite wise and seasoned. Hearing things like "I'm making tools I use" and "I'd rather be small and opinionated" or "I'll take paying customers over droves of free users" makes my heart warm. Congratulations and good work -- ignore haters and people with "suggestions" after their cursory 30-second glance at your work you've been eating / breathing for 3 straight years. My go-to response to such things has become "wow in X years I didn't think to google 'note taking app', thanks for that amazing suggestion!" :P (end salty solo-dev rant)
5 comments

Your note made me confront my own self-doubt. Time to dust off that old code-base
You don't need to get all the customers, you just have to find your customers.

As long as you find enough of them, you'll be ok.

You are wise to avoid trying to make an everything for everyone app. No one will want to use it.

and good for you! I have so many projects that have never seen a customer but I spend time polishing and creating them anyway.

I don't build things for other people. I build them for myself. If someone buys it great, if not, it doesn't matter. I did this for myself.

> Basically all the comments here are just critiques.

That's not how the thread looks now at all. The contrarian dynamic strikes again? https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

This attitude you applaud is Emersonian self-reliance. I agree it's refreshing to see it.
Indeed, I was wondering what familiar sense of righteousness was stirring while reading this comment:

http://www.gutenberg.org/files/16643/16643-h/16643-h.htm#SEL...

Always worth a(nother) read.

> Basically all the comments here are just critiques.

Welcome to hacker news!

I'll agree, however even rude critiques can often be useful if you can disengage your emotion chip.
Critiquing is a skill. The onus is as much on the critiquer to formulate their critique in a constructive, actionable way as it is on the critiquee to take the critique in stride.

That said, good crit skills are very hard to develop, and environments where effective critique sessions can be carried out very hard to build (because it’s fundamentally about trust). And it’s skill that is just not taught in engineering; people familiar with critique will be mostly people who went to art school, and even then many art schools do a pretty bad job at teaching it (I had a design teacher who, during critiques, would make students... vote on their favorite /facepalm).

Sure. However, to get feedback for a new project you probably need all you can get. Getting any at all can be surprisingly difficult.

Therefore one rarely can throw out the negative comments. Perhaps copy them to a file of notes and edit them to their core essence to minimize the sting.

Feedback from total strangers is overrated. You have no clue where their feedback comes from (are they a prospective user? Some grumpy programmer who just wants to rant about your choice of framework? A product designer used to operating in a certain environment that just doesn’t apply to you? etc). Separating the wheat from the chaff from anonymous posters is tricky business.

Thinking of it as good feedback vs bad feedback based on the feedback itself is also not the right way to go in my experience. Good feedback is anything that observes the way a particular problem was solved, and proposes an alternative way of solving it, or reframes the problem altogether (identifying a problem that was not solved can be valuable too, although the line is blurrier). Bad feedback tends to be, well, anything that is not that.

But hey in the end, whatever works for you.

You’ll still have to filter it on other criteria as well, agreed.