One thing I'm realizing is that you can quickly spend tens if not hundreds of thousands of dollars building products only for no one to use them and the money basically having gone to waste.

Def feels like the most expensive game of trial and error to ever exist.

If you think you need to spend X amount of weeks/days/hours working to launch the first version of something, really start to believe that X/2 and X/3 is likely more optimal.

I've progressively learned this over the years from values of X = 4 months, then 1.5, then 3 weeks, and so on... I launched the initial version of /amp after a few days, the semantic search after just 2. I launched the AI-generated homepage (ampcast.xyz/news) with about 3 hours of work on the first prototype - it turned into one of the top launches on the network that day, but I was genuinely surprised and was expecting just a few people to try it out and give me feedback, and instead I've had over a thousand land on the page that day.

Shaving scope is its own challenge - but unnecessary delay in launching hurts your learning. Launch faster.

For software startups (not hardware) you should really shave the scope down to a series of tests, not a full blown bells and whistles singular product launch. I like what @nt said about it

building /amp. prev: 2x founder, improbable, github, amazon. ntik.me

Onchain is the new online - FID 206 -  Building /coop-recs

For software startups (not hardware) you should really shave the scope down to a series of tests, not a full blown bells and whistles singular product launch. I like what @nt said about it

https://warpcast.com/nt/0xe49c8a94