131–140 of 225 posts
I think there's your first problem right there. I recommend seeking dev communities on more federated social networks. I have found there to be more support and less clout/lore building than on Twitter. And supportive communities ship products!
Earlier quoted context omitted.
Exactly, it's the opportunity cost. When I was a young adult and especially a teenager, I spent a lot of time making things out of pure desire to because I didn't have to think too much about my financial situation (present and future). That unfortunately gave way with age, and now ~15 years later whenever I engage with these activities there's a voice in the back of my head nagging, asking how doing those things ins…
I am in this boat with you. How do we get out?
Earlier quoted context omitted.
Exactly, it's the opportunity cost. When I was a young adult and especially a teenager, I spent a lot of time making things out of pure desire to because I didn't have to think too much about my financial situation (present and future). That unfortunately gave way with age, and now ~15 years later whenever I engage with these activities there's a voice in the back of my head nagging, asking how doing those things ins…
I am in this boat with you. How do we get out?
At 4 million in the bank (and various assets) you should be good to "escape," if by escape you mean "not need to sell your labor to live" anymore. 4 million gives you more than enough residuals to live off until death. Less if some of that is in property so you don't have to pay rent. Less if you retire to southeast Asia and engage in geographic arbitrage. You spent years paying for carrier groups and precision missiles, why not reap the rewards?
So far as I can judge, this is the only way the system permits escape.
If you're interested in permitless escape, one of my favorite introductions to the subject is "Walkaway" by Cory Doctorow, a wonderful amalgamation of hacker culture, anarchism, sustainability, anti capitalism, and communism. Even if you think some of those are dirty words, if you're at all interested in EV tech, 3d printing, batteries, solar, zero trust ID, or transhumanism, you'll probably enjoy that book. He basically just answers every "but what if..." you could think of for a group of hackers living in an abandoned rust belt town.
Personally I'm right now very interested in food forests and tech projects researching local supply chain production of equipment, such as https://www.opensourceecology.org/gvcs/ the global village construction set and https://simplifier.neocities.org whoever this person is that's been documenting their efforts building things like solar panels and circuit boards in their garage from raw materials for nearly the last decade.
Counterargument: I started Canny and we were a "build in public" startup early on. Building in public was an invaluable marketing channel in the early days. When you are just launching your product, it's really difficult to get those first users and any awareness at all. If your target audience includes other people in tech, then building in public can be great marketing channel. Posting about your ideas or your prod…
On the contrary, I wouldn’t be using Capacities if they didn’t have their entire development roadmap on your product, so thanks
Anecdotal, 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,…
https://en.m.wikipedia.org/wiki/Crossing_the_Chasm
Book by Geoffrey Moore.
quoted a lot by startups for a couple of decades plus.
had read it some years ago. quite interesting ...
Earlier quoted context omitted.
> 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. Sounds a bit like a variation on Conway's Law. https://en.wikipedia.org/wiki/Conway%27s_law
There must be some named law that states that the set of people you listen determine most of your thoughts. But it's something way wider in scope than Conway's Law. There are some proverbs, because it's a very old observation. But there must be named laws too, because it's a very common observation.
Anecdotal, 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've seen so many indie hacker types who are allergic to talking to (would-be) customers, seeking validation exclusively from other indie hackers, who would never be customers.
Saw a tweet the other day of someone saying "to find a good business idea, first tweet about it and see if it gets love."
1) what
Of course there are outliers like those who keep sharing their MRR, ARR, etc and then down the line sell an e-book on how to replicate their "success". I have followed enough "baits" to notice the pattern and ignore.
Earlier quoted context omitted.
I am in this boat with you. How do we get out?
Great question. The feeling clearly isn't based in logic; somehow watching a TV show or playing a game (neither of which is financially productive) instead of working on "just for fun" side projects doesn't elicit the same mental response unless I really couch potato out and do those things for hours on end. That makes it a bit more difficult to work with.
Of course, this isn’t how it actually seems to work - there is some truth to it for most people, but if you “overdraw” from one bucket and “neglect” another bucket, they will change sizes.