3 ms·
Are you sure you totally disagree? The author seems to mostly agree with your first point -- don't spend too much effort or complexity on scalability until you
by Johnny555 10y ago
Are you sure you totally disagree? The author seems to mostly agree with your first point -- don't spend too much effort or complexity on scalability until you actually need to scale:
If we focus on scale too early, we sacrifice a lot of the agility that we need early on. We need to think about our growth as getting more cargo on our journey. With each new customer we get a bit more valuable. We also get heavier and less agile. Our job as engineers is to patch the holes in the hull as we find them, and scale the size of the infrastructure at the right times.
- falsedan 10y ago> Are you sure you totally disagree? An extremely bad-faith reply (calling my opinion and understanding wrong), but I will attempt to reply: His recommendation is to avoid complexity, because it will make it hard to scale later. I think complexity is fine, because 1. above + 2. if you're really worried about future scaling.
- hyperliner 10y agoFlaming not necessary. You were not called "wrong." You were asked whether you considered the possibility that you and the OP could be in agreement at least partially. PEOPLE: can we not take everything so personally please? It's killing the country and some good HN threads. <EDIT> And even if you were called "wrong," who cares? it probably just means that your argument "could be wrong" so it's not you. And if it's you, then consider it a great anonymous tip for life improvement! And if you prove that someone else's argument is wrong, then guess what: you just helped a fellow human!