I think you’re being disingenuous and deliberately trying to refocus the conversation on something else now.
He literally said “if you vote for me, you won’t need to vote again”. It’s not an ambiguous statement and doesn’t require extra context. Everything else you said didn’t really have anything to do with it.
I think at that point founder taste comes in. “Strong opinions loosely held” comes to mind, in that you should already have some pretty strong ideas about where you want your product to go. Otherwise why build it? or maybe, why you specifically?
Being open to being wrong and course correcting when enough people tell you so is the loosely held part.
Go looking for them wherever you think they might gather or hang out (online or in person). Reach out to those who seem like a good fit and ask them about the problem(s) they’re having that your product solves. Once you know if your product would actually solve it well for them, tell them about it in earnest.
If you’re doing that honestly, where they really have that problem and you actually have a good solution, you’d be a jerk not to lightly pitch it at that point.
You could probably do that up to 100 or so customers reasonably easily.
Good advice. Do you think the part of point two about building every feature request might be a bit risky for some solo folks?
It’s easy to get carried away building every request, especially with early adopters who likely aren’t actually invested yet but may be excited about their own vision for it.
My personal experience is that too much of it leads to the product becoming a sort of shapeless, unwieldy ooze. Or perfect for one customer and few others. Some things can be tough to undo later too, so you might end up supporting them a lot longer than you’d like.
It makes connecting user domains to your app easy and reliable at any scale. Each Approximated user gets the own globally distributed, managed cluster of servers with its own dedicated IPv4 address. Includes (unlimited) edge rule features, DDoS protection, webhooks, and more. Make a simple API call, tell the user to point an A record at the IP, and it’s connected to your app with its own SSL certificates.
Built/building with elixir and phoenix, which has been fantastic.
We can also invert that by asking: does a student become smarter by writing their essay on their own?
I would argue that the answer to questions is no. It depends on how you define “smarter”, though. You would likely gain knowledge writing the essay yourself, but is gaining knowledge equivalent to getting smarter?
If so, you could also just read the essay afterwards and gain the same knowledge. Is _that_ smarter? You’ve now reached the same benefit for much less work.
I think fundamentally I at least partially agree with your stance. That we should think carefully before taking a seemingly easier path. Weighing what we gain and lose. Sometimes the juice is, in fact, the squeeze. But it’s far from cut and dry.
Isn't the main problem that this change forces all software development, regardless of purpose, to be classified as R&E and therefore forced to be amortized?
He literally said “if you vote for me, you won’t need to vote again”. It’s not an ambiguous statement and doesn’t require extra context. Everything else you said didn’t really have anything to do with it.