Building a SaaS is basically one long decision tree:
• come up with the idea
• sanity-check if anyone actually needs it
• name it (then rename it three times)
• buy the domain
• design a logo at 2am
• scope the MVP
• cut half of it
• pick a stack
• second-guess that
This is why they fail at weird edge cases but they nail complex reasoning. They’re approximating understanding through pattern matching. Like, the fact that this works at all is the miracle. We built something that fakes comprehension so well we can’t tell the difference.
Everyone’s trying to build the next billion dollar company.
Meanwhile someone’s making $30k/month solving a problem so niche that VCs won’t even take the meeting.
Guess who’s happier.
Well, Apple might be playing a different game entirely. I don't know. But like, why compete with OpenAI's burn rate when you can wait for commoditization? They need to lead in implementation though.
I guess Apple's cultural DNA is "perfect or nothing" That works for phones and
I'm so bullish on bootstrapping.
There’s a ton of reasons but the main one is that it forces profitability from day one.
No runway to burn, no board to impress. Build something people pay for or die trying.
When it's your own money disappearing, you find product-market fit
I strongly believe that every dev should ship something solo at least once.
Not because it’ll make you rich.
Because it forces you to think about everything, like design, onboarding, pricing, copy, support.
Suddenly, “just writing the code” feels like a luxury.
You see how
Code is the easy part. Distribution is the game.
You can build 10 projects in 3 months, but if nobody sees them, they don’t exist.
Indie hacking is 20% building and 80% making people care.
Marketing is just showing your work, over and over, until someone pays attention.
