I really dislike that so much of hacker culture is $$ focused now. 1. Being a hacker means walking the world being constantly dissatisfied by all of the inefficiency you see on a daily basis and wanting to fix it. 2. Being a hacker means feeling like most of the software world is fraudulent and you are going to build a solution that actually works. 3. Being a hacker means building something because it is fun or cool.…
Does “building in public” work?
51–60 of 225 posts
Re: Does “building in public” work?
#52I really dislike that so much of hacker culture is $$ focused now. 1. Being a hacker means walking the world being constantly dissatisfied by all of the inefficiency you see on a daily basis and wanting to fix it. 2. Being a hacker means feeling like most of the software world is fraudulent and you are going to build a solution that actually works. 3. Being a hacker means building something because it is fun or cool.…
If no one will pay for the solution, the problem might not be that important.
The ONLY reason I have any interest in someone's output is if it is something they themselves actually care about, what they actually think, etc. I want to know what they have to say. There is absolutely no value in them trying to say what they think I want to hear, worse, what they think most people want to hear.
The second someone says "tell me what you want" I'm out. If I have to tell them that I'm interested in x, and then they go investigate x, what value is that to anyone? What insight can they bring to me about the topic of x? Why should I care what they have to say about x when 2 seconds ago they had no knowledge of it? No one's mere personality is so awesome that just having them do the same exact google search I can do and read the same exact intro material I can read and blatting out their initial reactions based on just that, results in something worthwhile.
Whether your numbers (or your sales) are good or bad, it is a factor to consider, but it can't be the fundamental point of your existence. You have to have some legitimate point that stands on it's own, and only then, maybe, you can live off of it somehow.
If you only care that you somehow get money, and don't care how, what value is that to me? Why would I as a customer give you money for anything? Even if you were trying to pander to exactly what I said I wanted, if I don't perceive that you are deeply knowldgeable and insightful and experienced in that topic, or at least maybe new but genuinely interested in working in that field or on that problem, but just trying to say yes to anything, no way in the world am I choosing you to supply that need.
Re: Does “building in public” work?
#53I really dislike that so much of hacker culture is $$ focused now. 1. Being a hacker means walking the world being constantly dissatisfied by all of the inefficiency you see on a daily basis and wanting to fix it. 2. Being a hacker means feeling like most of the software world is fraudulent and you are going to build a solution that actually works. 3. Being a hacker means building something because it is fun or cool.…
If no one will pay for the solution, the problem might not be that important.
Re: Does “building in public” work?
#54I really dislike that so much of hacker culture is $$ focused now. 1. Being a hacker means walking the world being constantly dissatisfied by all of the inefficiency you see on a daily basis and wanting to fix it. 2. Being a hacker means feeling like most of the software world is fraudulent and you are going to build a solution that actually works. 3. Being a hacker means building something because it is fun or cool.…
There's another very large subgroup you're missing: the hackers that build things (even for $0) because they're fun/cool, not because they solve a specific annoying problem/inefficiency.
Re: Does “building in public” work?
#55Re: Does “building in public” work?
#56I really dislike that so much of hacker culture is $$ focused now. 1. Being a hacker means walking the world being constantly dissatisfied by all of the inefficiency you see on a daily basis and wanting to fix it. 2. Being a hacker means feeling like most of the software world is fraudulent and you are going to build a solution that actually works. 3. Being a hacker means building something because it is fun or cool.…
There's another very large subgroup you're missing: the hackers that build things (even for $0) because they're fun/cool, not because they solve a specific annoying problem/inefficiency.
Re: Does “building in public” work?
#57Earlier quoted context omitted.
If no one will pay for the solution, the problem might not be that important.
Or: you've built 67% of a solution, and it only really crosses into financial sense for most buyers once you pass 89%.
Re: Does “building in public” work?
#58Anecdotal, but it seems like all the people who “build in public” end up trapped by their chosen distribution strategy. What I mean by this is, if you’re building in public there’s a 99% chance you’re going to end up building products for other indiehackers who are interested in following people who build in public. This means you’re probably going to end up building yet another micro-Saas dev tool (Saas boilerplate,…
I see your point, but I would disagree with you somewhat. Every new startup needs to navigate the transition from early adopters to bigger names and/or more mainstream users who give you credibility and higher revenue potential. But it’s almost always done as a stepping stone approach. You need to get the early adopters first or else none of the rest matters. Doing this is not easy so any conceivable advantage is wor…
If we take B2B products for example, it's super common to niche down into a specific industry and then expand out to adjacent ones, and so on.
But the build-in-public industry/niche is unique in that those customers aren't "real" businesses with "real" problems. Most of the followers are wantreprenuers with imagined problems.
So the risk is, instead of building a solid foundation to expand from, you might just be building the wrong thing altogether and doing it on quicksand (those pyramid scheme dynamics I was talking about).
Re: Does “building in public” work?
#59I do work with the garage door open though. I share screenshots, ask for feedback, and show off the little details I spent a lot of time on. It’s basically a DVD commentary for the stuff I am about to release
This attracts the right kind of people, and sparks the right kinds of conversations. I am basically involving fellow builders in my design process, and hyping what I am working on to my audience and industry peers. It is a good way to make friends.
Re: Does “building in public” work?
#60I really dislike that so much of hacker culture is $$ focused now. 1. Being a hacker means walking the world being constantly dissatisfied by all of the inefficiency you see on a daily basis and wanting to fix it. 2. Being a hacker means feeling like most of the software world is fraudulent and you are going to build a solution that actually works. 3. Being a hacker means building something because it is fun or cool.…