3 ms·
It's not about the hardware. It's about what happens when it breaks--which it will--and when you need stuff you can't reliably build off the top of your head--w
by eropple 9y ago
It's not about the hardware. It's about what happens when it breaks--which it will--and when you need stuff you can't reliably build off the top of your head--which you will.
The axe you're grinding is profoundly weird, and indeed a large part of my business is because the stuff we build is extremely cost-competitive with dedicated hardware. Difference being that I can open up the console and start shooting servers and nothing breaks. You're not saying the same with the overwhelming majority of naive "dedicated hardware" deploys, especially at the levels of skill and expenditure that small companies can employ.
- _jal 9y agoI don't see anything "profoundly weird" about it (a bit specific, maybe, given the rest of the conversation). You're right, of course, about naive deployments. But it just isn't that hard to build reliable systems, assuming some experience. And if you're doing anything more interesting than pretty CRUD forms (say, atypical storage or bandwidth requirements), DYI becomes much cheaper, fast. To reiterate, yes, you need someone who knows what they're doing on the systems end. But you will anyway at some point, and making that hire earlier can pay for itself.