Doing your own research, visiting libraries, reading reviews, etc. These are the best way to find books that you never would have found otherwise.
Otherwise you're going to end up with the same old stuff (SICP, Release It!, GEB, Code Complete, blah blah blah). Those books are actually good but they are on every single list and even worse, some "modern classics" are actually complete dreck. You might impress your developer friends but you won't advance yourself.
For example when I was studying for my PhD in signal processing and machine learning (before machine learning became popular again) I had to learn a lot about functional analysis. I also needed to learn a small amount of measure theory; and to go appreciably deeper in to time-frequency analysis, probability, and statistics, than I had before.
I discovered many masterpieces of my own accord. I never would have seen them because one lesson I learned during my literature review and actually doing research is that very few people actually read the books and articles they cite. They merely copy bibliographies from one ancestor article to another without knowing why.
I had an epiphany the other day. These books offer expansive references to where the author found or sourced their material. Looking through there is a great place to start once the standard books have been completed.
I was always amazed at how few people used the library at university. Lots of people used it as a study space, but hardly any actually took out books unless it was an urgent loan for something.
Given how expensive textbooks are, it's well worth taking a bunch out and deciding if you actually want to buy any of them. Especially books outside your field (eg as a physicist I would take out CS books).
Even if you don’t explicitly copy it my understanding is there is certain references you are just “supposed to” cite. That’s not then same as having good exposition of course.
>>visiting libraries
This. Lacking the "efficient optimisation" of online search, you may actually discover real, valuable information from original sources.
> Those books are actually good but they are on every single list and even worse, some "modern classics" are actually complete dreck. You might impress your developer friends but you won't advance yourself.
I don't get it. If these are good books and you have not read them, how will you not advance yourself by reading them?
“The Mom Test” by Rob Fitzpatrick is in my mind the most revolutionary and essential business book for indie hackers in the last 20 years. It would have saved me $1.4 million in my attempt to beat craigslist at its own game a decade ago.
It illustrates in the most logical progression a set of easily implementable steps to ensure that your own confirmation bias doesn’t sink your company.
I just want to recommend a service called eReaderIQ. It's a price tracking service for eBooks. Basically any book you've wanted to read has been available for $3 or less in the past year. I've saved a ton of money with this service.
Downloading copyrighted content from such sources is legal in many jurisdictions. What's illegal in most places is uploading said content to others. This got conflated 20 years ago when peer-to-peer file sharing developed, where you are downloading and uploading at the same time. But the web is not peer to peer.
Here's another vote for The E-Myth. I would recommend it to everyone working in any business. For example, if you are considering joining a company, you can use the principles described in the book as a way to evaluate that company. If you are starting something or a business owner trying to grow, it describes accurately the mistakes you might make and a path forward.
In a similar vein, Built To Sell (John Warrillow) was eye-opening for me when I first read it, focusing on building processes and systems so that you can remove yourself as a roadblock to increase chances of success. Almost an “if you love them, set them free” philosophy and written in a very readable style.
One option no one mentioned: No book. Do first, read later. Experience trumps reading every time. At least I think that many people just started to work on something instead of reading first.
My favorites, which I read only after I launched a product:
Rework. About improving a product.
"This is Marketing" from Seth Godin. To get the right mindset about who the audience is.
Except I still haven’t started working on it :grimacing:
I’ve been meaning to update this for years but hard to find the time. Right now MicroConf and TinySeed are keeping me busy, but it continues to be on my long-term list.
The Dip by Seth Godin is perhaps the essential book for an 'indie hacker'.
It's about identifying the difference between dips (good business ideas facing inevitable challenges) and cul-de-sacs (poor ideas that are not going anywhere).
Choice quotes:
> Strategic quitting is the secret of successful organizations
> Extraordinary benefits also accrue to the tiny majority with the guts to quit early and refocus their efforts on something new
> Quit the wrong stuff. Stick with the right stuff. Have the guts to do one or the other....the opportunity cost of investing your life in something that’s not going to get better is just too high
For me most interesting are autobiography books where author is sharing his path from the start, instead of giving "10 rules of success" (which is his subjective insights summary of what worked for him).
The beauty of autobiography books is that we need to aggregate (generalize) these key insights based on the raw story ("subjectively raw" of-course) and our current situation.
The most valuable part for me is about overcoming hard problems.
The #1 book in my list is "Shoe Dog" by Phil Knight (The Founder of Nike). There is also an audiobook where Phil himself is read the first chapter.
I was a little confused what they called an "indie hacker" and how they dedicated an entire website to such people. It's not conflating "hacker" with "startup founder". It's defining "indie" as "small startup founder" and "hacker" as "person who works in the software industry".
As the exact target audience, it's kind of neat to me.
My favorite from the list is Traction. It is quite short and it clearly fit the type of person that I am: Developer who like to sit down and create some products, but haven't really thought about channels and distribution systematically before.
The Hard Thing About Hard Things is supposed to a good book for start ups/indie hackers. I listen to a lot of podcasts in this area and it's mentioned quite a lot.
I like this book because I like anecdotes from tech startups. I especially the following story [0] as it has profanity, email judo, earnestness, and candor...
“Then, just two weeks before the launch, Marc, without telling Mike or me, revealed the entire strategy to the publication Computer Reseller News. I was livid. I immediately sent him a short email:
To: Marc Andreessen
Cc: Mike Homer
From: Ben Horowitz
Subject : Launch
I guess we’re not going to wait until the 5th to launch the strategy.
— Ben
Within 15 minutes, I received the following reply:
To: Ben Horowitz
Cc: Mike Homer, Jim Barksdale (CEO), Jim Clark (Chairman)
From: Marc Andreessen
Subject: Re: Launch
Apparently you do not understand how serious the situation is. We are getting killed killed killed out there. Our current product is radically worse than the competition. We’ve had nothing to say for months. As a result, we’ve lost over $3B in market capitalization. We are now in danger of losing the entire company and it’s all server product management’s fault.
Next time do the fucking interview yourself.
Fuck you,
Marc”
This entire book is literally about companies that focus on deliberately growing but still staying excellent. Many were profitable and didn't raise a lot of outside funding. Many also were strongly owned by employees.
Keep in mind that IH'ers are trying to start their own independent internet-based bootstrapped businesses. Having joined the IH community recently, I can attest that the business side of things is where most IH'ers are lacking in terms of achieving that goal (myself included). Their technical skills tend to be "good enough". Hence the value placed on these types of books. Hope that helps to explain.
If you liked E-myth, the Road Less Stupid is a great one for small companies or startups especially if you're struggling to move from an operator to an owner role
Not super familiar with the space, but ReWork by Jason Fried and DHH, founders of BaseCamp (DHH made Ruby on Rails), was pretty good. They provide a very different take on business and startups than typical on HN. They are almost anti VC, and really have some good points when it comes to making something and running a company differently than typical enterprise and startups do.
The War of Art is undoubtedly a self-help book, and so is How to Make Friends and Influence people. Both contain little more than trivial platitudes IMO. I have not read the other books, but from the abstracts it looks like several more can be considered self-help books.
I was hoping for hands-on books like "The Art of Electronics" by Horowitz & Hill or similar.
Or at least something like The C Programming Language. Or at least Introduction to Linear Algebra by Gilbert Strang. Or at least The Theory of Relational Databases by David Maier.
It largely refers to software developers who make a living from one-or-more revenue-generating businesses they've built themselves.
This type of person is distinct from people who are employed full-time (or on a long-term contract) or who fund a business with major outside investment.
The key values of the indie-hacker community seem to be around building sustainable businesses that can fund an individual or small team to build valuable products for a small-but-substantial niche of customers, as distinct from the "boom or bust" approach of VC-funded, rapid-growth-focused startups.
That was the first thing I tried, but since the only relevant hit is the indiehackers side leads me to believe its s made up term and not actually a thing, and I wanted to confirm that. But thank you for your informative reply nonetheless, obvious you put a lot of effort in it!
Otherwise you're going to end up with the same old stuff (SICP, Release It!, GEB, Code Complete, blah blah blah). Those books are actually good but they are on every single list and even worse, some "modern classics" are actually complete dreck. You might impress your developer friends but you won't advance yourself.
For example when I was studying for my PhD in signal processing and machine learning (before machine learning became popular again) I had to learn a lot about functional analysis. I also needed to learn a small amount of measure theory; and to go appreciably deeper in to time-frequency analysis, probability, and statistics, than I had before.
I discovered many masterpieces of my own accord. I never would have seen them because one lesson I learned during my literature review and actually doing research is that very few people actually read the books and articles they cite. They merely copy bibliographies from one ancestor article to another without knowing why.