Hacker News Reader

Comment by n72 | Hacker News Reader

The great majority of people shouldn't read these — not because they're not good books or don't increase one's chances of startup success (they may or may not — I have no clue), but because the great majority of people will think they're doing startup stuff by reading them. It's confusing activity for accomplishment. If you do read these, keep in mind the entire time you're reading these you're not working on your startup. In other words, be very cognizant of the fact that you may very well be procrastinating.

View on HN

This is a ridiculous comment. Read and learn from other people. Just don't substitute that for learning from experiment, instead use it as in a complimentary manner.

My interpretation of n72's comment: These books aren't worth reading because they make you focus your time and mental energy on activities that make a good startup, rather than activities that make a good product.

There's a temptation, when you're an early-stage startup with little direction, to start "playing house"[0]: Trying make your startup look and feel like all these other successful startups you've seen, and, by reading more books, getting positive feedback for doing those things.

There's obviously value in wisdom gained from those who've walked down this road before. But it's not worth obsessing over how to make the perfect startup. It is worth obsessing over how you can be delivering more value to your customers.

[0] PG's term http://paulgraham.com/before.html

It is indisputable that more knowledge is a good thing. My point is merely that "in a complimentary matter" so very often becomes "instead of", because of the insidious nature of procrastination.

While I agree with your general sentiment (a lot of the readings on this list strike me as being startup porn), there are some readings -- and these could be in a list -- that are good for an early startup founder to read in moderation.

Topics would include "fundamentals" like different ways to talk to customers or different ways to test product-market fit (possibly in a very efficient way). These may seem very obvious to people who have done them or know someone who has, but they are not obvious to a lot of people.

I will also add that once product-market fit is achieved and the business is officially a thing, there are a wide range of readings that would be useful for a (relatively) new founder. Topics would include things like sales, fundamentals of management (this topic is really not obvious or widely known to a lot of young, gifted people who are often founders of decent startups), and basics of business operations. Granted most of these things can be found on one's own, but a tight, curated list (this one does not seem to be one) would certainly have some value.

Note to the budding startup founders out there: Reading in moderation is fine. Always read for a purpose. Stay away from the startup porn -- it will take you down a path of failure.

Pick a spot where it's hard to be objectively productive, e.g. on the elliptical at the gym (hard to code), or train (uncomfortable if packed train, too much stimulus). Read there. When you are home, work.

Personally, I don't track time spent reading, unless it's to understand how to solve a specific problem.

I think the great majority of people should read these books - in a matter of hours they can be a fly on the wall. Mistakes cost money and time. Also, most people aren't around people who have had success in this avenue, so being 'around' the authors does help to make their goal real.

To be fair, reading comments on the internet is also a waste of time.

N72, I think there is some truth in what you are saying. I would just pay attention in phrasing this in the right way. After all, even if you 'just' read all this resources, I would not consider it a waste of time.

One chapter per 10% growth of the company.

Product always goes first.

Reply on news.ycombinator.com