I build software products
Dormant Last read · last published · next check
Read 5 days ago and current, but nothing has been published for 17 months.
Learn to code. Because it teaches you how to think. Learn to leverage AI. Because it helps you get ahead of competition. Learn to build. Because the best way to predict the future is to invent it. Learn to sell. Because even the best ideas don’t spread themselves.
I realize the reason I like building is not just because I’m a builder. It’s because software products are how I express my creativity. It’s like a poem to a poet, a song to a songwriter, a painting to a painter… Software is
When building is easy, we should spend significant more time to figure out that “something people want”. There are multiple approaches to do this: - Do customer development before building. Jason Cohen famously interviewed 50 potential customers before writing a single line of code. - Build an extremely simple (but
I think the good path for a software engineer to become a solopreneur is to be a product engineer. Back when I was starting, there is no clear definition of a product engineer. But if you're one of the first engineering hires of a startup (founding engineers), chances
Don't treat your product launch as a sales event. Treat it as a celebration. And what would make a great celebration? A compelling story! How to tell a compelling story for your startup launch? Frame it as a journey where your early users are the heroes. You are
After 15 years building software products, I think the best thing I’ve developed is a taste in technology Not “this tech good, that tech bad” kind of opinion But more like “oh this one really fits my mental model and it makes me more productive&
Nick on Twitter asked, what is the difference between "Lifetime" vs "One-time payment"? I'm struggling with how to the license for my product ( @PopClipApp ) and I'm interested on how you see the difference between "lifetime" & "one-time
It is hard to quit your comfortable job. Doesn’t necessarily to be a high-paying job in big techs. The doubt. The fear. And so many what-ifs… I believe people who are on the fence are usually not sure what they want: freedom, uncapped upside, fame,
"Indie hackers are newbie entrepreneurs" Can't remember who said that, but I find it so true. When you position yourself as a newbie, it opens a lot of opportunities: → You learn everything with an open mind The Dunning-Kruger effect happens to us all, sometimes
Submit early Don’t wait until you’re 100% happy with your app Submit early so AppStore Reviewers would find issues sooner and you could fix them quicker I did this with PDF Pals even when I knew it would be rejected “But what if it gets
“Scratch your own itch” is a good strategy for startup founder, only if it got some sort of outside validation. This is especially true for indie hackers. Just because we have a problem to solve, doesn’t mean others find it a problem. And even when it&
💬 "Coming up from the bottom is not a long period of being fat and comfortable, then a sudden need to become hungry. It is full of spikes of anxiety about how dire your situation is." — Louie Bacaj I was born and raised in a poor village
One thing I learned about winning is small wins would lead to bigger wins. With perseverance and a growth mindset, all those wins would lead to a huge success. Seek those small wins when you’re just starting out.
I was mostly a self-taught developer, and am now trying to be a self-taught marketer. I remember how hard it was to start a software project: there were just so many things to learn. The computer science fundamental concepts, while important, are super boring and not always practical.
