7 ms·

Rule number one. Use what you know. Rule number two, use what can last you for the first three years. Rule number three, build with considerable haste. Don’t

Rule number one. Use what you know. Rule number two, use what can last you for the first three years. Rule number three, build with considerable haste. Don’t choose anything from 1 & 2 that limits that. Everyone’s preferences from there are all relative. If I was building something from scratch today I’d use cloud run for containers, stripe for payments, datadog for monitoring and APM, RoR for my app, Postgres, bigQuery for analytics (if needed), Vue for my frontend, postmark for email, cloudflare, and probably a mix of other tools as needed. If I was screwing around and not trying to use what I know, I’d probably try to build as much as I can on top of vercel and planetscale. Vercel makes killer projects and tools, and I can see planetscale being a market leader in 10 years that everyone uses by default. But, that’s a big bet to make when starting a new company.

cultofmetatron 5y ago
the big caveat in planetscale is that you pay per row READ. so make damn sure you use every index afforded to you
methyl 5y ago
Using what you know is not only valid choice and you can build a successful startup while learning at the same time [1]. Using what you know might be a valid choice when you are much more excited with the business itself rather than building the product, but I think it’s rarely the case for developers who want to try enterpreneurship. [1] https://lucjan.medium.com/choose-exciting-technology-e735bba08acc https://lucjan.medium.com/choose-exciting-technology-e735bba...
codegeek 5y ago
I disagree slightly. It depends on where you are. If you are literally starting out like OP, forget number 2 and 3. Only focus on #1 because if you don't get a few paying customers soon, you will be dead anyway. Focus on surviving first. Forget about 3 years. If you can make it 12 months, you are doing great. Rule #2 is important but not until you have a few paying customers and some product market fit. Rule #3 I would say comes way later. way later.
- reducesuffering 5y ago
  #3 is actually crucial because if you only go by #1, and you only know C++, I will not get far in making a full stack app.
- rmbyrro 5y ago
  Don't you consider #3 (rapid development) can be crucial in the quest to get paying customers and survive the first 12 months?

cultofmetatron 5y ago

the big caveat in planetscale is that you pay per row READ. so make damn sure you use every index afforded to you

methyl 5y ago

Using what you know is not only valid choice and you can build a successful startup while learning at the same time [1]. Using what you know might be a valid choice when you are much more excited with the business itself rather than building the product, but I think it’s rarely the case for developers who want to try enterpreneurship. [1] https://lucjan.medium.com/choose-exciting-technology-e735bba08acc https://lucjan.medium.com/choose-exciting-technology-e735bba...

codegeek 5y ago

I disagree slightly. It depends on where you are. If you are literally starting out like OP, forget number 2 and 3. Only focus on #1 because if you don't get a few paying customers soon, you will be dead anyway. Focus on surviving first. Forget about 3 years. If you can make it 12 months, you are doing great. Rule #2 is important but not until you have a few paying customers and some product market fit. Rule #3 I would say comes way later. way later.

reducesuffering 5y ago
#3 is actually crucial because if you only go by #1, and you only know C++, I will not get far in making a full stack app.
rmbyrro 5y ago
Don't you consider #3 (rapid development) can be crucial in the quest to get paying customers and survive the first 12 months?