3 ms·

You're arguing against a strawman here. No one's saying "let's do stuff the stupid way!" - they're saying hey, let's focus on getting users before fleshing out

• hunter23 9y ago
  Yes exactly! The point is you don't build a scalable app until you have a scalable business idea. The first iterations of a startup are about testing different ideas, not about building sustainable architecture. Unless you are building a technical work of art, it's all about finding the right product.
  • rbanffy 9y ago
    Some decisions need to be made early on. You may be fine with MySQL, but you need to think about decoupling different parts of the process and to think about the implications of delays on the interfaces from the start, even if they aren't there. Most likely you'll never reach Google scale, but, you'll be happy you did that as the application grows more complex and you don't have to test every part of it for each tiny change.
  • Retric 9y ago
    Some ideas can't scale. Ex: If your building a game with N players that can see each other walking around then that's N^2 updates. Now, plenty of ways of dealing with that problem, but it's something to keep in mind even if you solution is not yet worth implementing.
• rbanffy 9y ago
  This is a relatively narrow scenario. Some applications "already made it". I'm helping build an IIoT solution that can process a really ludicrous number of measurements per second. If the code is optimal, we have a pretty positive impact on the company's bottom line. If it's not, we'll become famous for being the first group to unwillingly enter Top500 territory.