3 ms·
OP has it backwards. What he calls "bad", I call "good". You shouldn't have to worry about things like systems administration, email, and scaling from the sta
by edw519 18y ago
OP has it backwards. What he calls "bad", I call "good".
You shouldn't have to worry about things like systems administration, email, and scaling from the start. If you are, you're probably not focused on the most important things and may well run out of runway before you ever really need them.
OTOH, if you focus on your app and your customers and are so successful that your infrastructure can no longer support you: what a great problem to have.
- swombat 18y agoltns, edw519 :-) Where have you been lately? Good to see we agree on something for once.
- edw519 18y agoHey, swombat. If I'm not writing text here, then I'm writing code somewhere else. (Either way, I'm a hacker at a keyboard.) When I read your comment here, I thought how much better you said the same thing. I don't remember disagreeing with you much, now I have an excuse to explore searchyc later today :-)
- swombat 18y agoWe have disagreed quite strongly on some project management topics... :-) (particularly to do with the need or lack of need for "business analysis") Happy hacking!
- johnrob 18y agoExactly. Show me one startup that had trouble scaling to meet demand, and I'll show you a hundred that built a scalable system that nobody wanted to use.
- sabat 18y agoIt doesn't need to be black-and-white. If you aren't thinking at all about running the business then you're going to go through a lot of unnecessary pain. Better to hire developers (who aren't blind to production issues) and then maybe more developers and then a good, forward-thinking, cooperative sys admin (a rare beast, unfortunately). If you pretend that production is a mere afterthought then you're likely to end up being Twitter. Successful, yes, but scrambling to stay in business (I'm not talking about the revenue model issue here).
- edw519 18y agoOf course. Whenever I design anything, one of the questions I always ask myself is, "How well will each alternative scale?" And the answer often has dramatic effect on the outcome. But I don't spend unnecessary money before I have to and if I spend more than 5 or 10 minutes thinking about scaling or optimization, I quickly snap back to reality and focus on my app. The trick (as in most things) is knowing where to draw the line.