3 ms·

Have you considered that you may optimize excessively and way too early? People who would buy your product do not care whether it's serverless or not. If peopl

Have you considered that you may optimize excessively and way too early? People who would buy your product do not care whether it's serverless or not. If people like product and it sells well, you will have time and money to refactor your product (I would still think twice before doing so). Consider this: > remoteok.io is a single PHP file called "index.php" generating $2,342.04 in a day. No frameworks. No libraries. If you want to start quickly with app that has signup and pay for content, consider this open source app: https://github.com/builderbook/builderbook https://github.com/builderbook/builderbook I am a co-author. If you really need passwordless-like flow, check out: https://www.npmjs.com/package/passwordless https://www.npmjs.com/package/passwordless

deadcoder0904 8y ago
I know RemoteOK very well :) I know people don't care whether it is serverless or not. But that's not the point. The point is reducing cost. Why should I pay for services I don't use? Why should I write the same code twice (once for server & once for serverless)? Although a lot of that would be same but I still need to write a lot of config to run serverless. Why should I worry about Scaling?
fefb 8y ago
Do you know how remoteok make money? Thanks
- FanaHOVA 8y ago
  Open the website and press Post a Job.
- gadders 8y ago
  https://www.indiehackers.com/interview/growing-a-community-for-digital-nomads-to-33-000-mo-126df0fc5e https://www.indiehackers.com/interview/growing-a-community-f...