4 ms·
1. Use whatever you already know. 2. Start building now. It’s okay not to write unit tests at the beginning. It’s okay to run everything on a single ec2 insta
by wenbin 5y ago
1. Use whatever you already know.
2. Start building now.
It’s okay not to write unit tests at the beginning.
It’s okay to run everything on a single ec2 instance.
It’s okay to not have “forgot password” flow when you launch your project v0.1.
It’s okay to ssh into server to deploy code at the beginning.
Many billion-dollar companies were using pretty bad software engineering practices at the beginning of their life (maybe first 5 years). Engineering is just a small part of a tech business.
- cpursley 5y ago> It’s okay to not have “forgot password” flow when you launch your project v0.1. There's no excuse for not having the ability to reset your password with so many turn key solutions and libraries available nowadays. But I agree with all the rest.
- kohanz 5y ago"There's no excuse" and "it's ok" are not mutually exclusive. The point being that if you have no customers, working on a password reset feature instead of marketing, can be a poor choice. I know of several bootstrapped SAAS that didn't add such a feature until reaching 4 or even 5 figures of MRR. They just did it manually for their customers until then. Not ideal, but it worked for them and is indicative of the mindset needed.
- cpursley 5y agoFair enough. I suppose it's highly dependent on the app.