3 ms·

I don't see the problem. If you get so far and then need to do something else, only then is the time to start worrying about doing something else. Until that po

I don't see the problem. If you get so far and then need to do something else, only then is the time to start worrying about doing something else. Until that point the focus should be on shipping a quality product that satisfies a need. Do that well enough and you will be in a position to start worrying about using better languages for certain problems. Almost every tech company that is slightly mature has multiple languages in production anyhow and they got there because they built stuff and shipped it.

blub 11y ago
The big question is if they got there because of the tools and practices they use or in spite of them. With enough money and talent one can use pretty much anything. And the problem with having to rewrite your stuff is that the company might go out of business while doing it. Assuming it's something complex, and not e.g. reddit (which I suppose is not at all easy to build as a full product, but at the end of the day is an online forum)
- rorykoehler 11y ago
  If your company goes out of business because you spend time re-architecting then you're doing it wrong. The thing with stuff like Rails is that we don't need money to start quickly. They are amazing for validating a business idea and doing fast iterative agile development which is the core to building a successful startup. Once you've done that and have either cashflow or serious funding you can afford to pull out some functionality into separate services with more appropriate architecture etc. For what most MVP's are, tools like Rails are very good as they optimise for build speed. Clearly they can't do everything and shouldn't be used for some things but for most web things they are a solid choice. Companies that optimise prematurely are far more likely to go out of business.

3 ms·

I don't see the problem. If you get so far and then need to do something else, only then is the time to start worrying about doing something else. Until that po

by rorykoehler 11y ago

blub 11y ago
The big question is if they got there because of the tools and practices they use or in spite of them. With enough money and talent one can use pretty much anything. And the problem with having to rewrite your stuff is that the company might go out of business while doing it. Assuming it's something complex, and not e.g. reddit (which I suppose is not at all easy to build as a full product, but at the end of the day is an online forum)
- rorykoehler 11y ago
  If your company goes out of business because you spend time re-architecting then you're doing it wrong. The thing with stuff like Rails is that we don't need money to start quickly. They are amazing for validating a business idea and doing fast iterative agile development which is the core to building a successful startup. Once you've done that and have either cashflow or serious funding you can afford to pull out some functionality into separate services with more appropriate architecture etc. For what most MVP's are, tools like Rails are very good as they optimise for build speed. Clearly they can't do everything and shouldn't be used for some things but for most web things they are a solid choice. Companies that optimise prematurely are far more likely to go out of business.