I guess "casual dress code" at startups these days means exposed feet on the table, right where your co-workers can see (and perhaps smell) them.
And why does he have a roll of toilet paper under his monitor?
31–40 of 58 posts
I guess "casual dress code" at startups these days means exposed feet on the table, right where your co-workers can see (and perhaps smell) them.
And why does he have a roll of toilet paper under his monitor?
Basically the Cloud is a stepping stone on your way to greater things. You may outgrow the cloud or you may find you have economies of scale where the cloud is becomes the expensive option. Recognise it and change your set up. TBH you should be doing this with all aspects of the business. Start in a room/garage, move to serviced offices, then rent your own building, then buy your own building (should it become financ…
It's a stepping stone for some companies. For many others, it's not (e.g. Netflix, Heroku). I see a false dichotomy here: start off with the cloud, then move to bare metal servers. If you've got an OLTP database that demands high-performance, you may need bare metal. Many companies don't, though. I've been a consultant to companies who've over-extended themselves on EC2 and ended up with huge monthly bills they didn'…
Content owners can and do screw Netflix with hardball negotiation tactics. Unlike cable companies, Netflix doesn't have a utility billing regime or local monopoly on services. So at any time, the need for large swaths of their IT infrastructure can disappear.
So what do you do? Put lots of liabilities on your books (datacenters, computers, SANs, etc)? Or rent it from someone?
>> That’s $324,000 a year. But for just $120,000, the company could buy all the physical servers it needed for the job What about power, cooling, rent in the building for the room you're keeping them in, backup generator, internet connectivity, administration costs (setup, repairs, installation), etc? >> “The public cloud is phenomenal if you really need its elasticity,” Frenkiel says. “But if you don’t — if you do a…
Earlier quoted context omitted.
And how many extra 'DevOps' people has the company now had to employ to manage these physical servers, and what is their annual salary? This never seems to be factored into the calculations.
That was my first thought, too. Physical hardware == more staff. Also consider the risk management of keeping your security up to date, and the opportunity costs of making it easy to use for developers. Spend some time in old-school enterprise, and you'll see just how much pain and grief can happen. Remember, Amazon built its cloud not for the public, but for itself! The cloud gave them a clean separation of duties a…
>> That’s $324,000 a year. But for just $120,000, the company could buy all the physical servers it needed for the job What about power, cooling, rent in the building for the room you're keeping them in, backup generator, internet connectivity, administration costs (setup, repairs, installation), etc? >> “The public cloud is phenomenal if you really need its elasticity,” Frenkiel says. “But if you don’t — if you do a…
And how many extra 'DevOps' people has the company now had to employ to manage these physical servers, and what is their annual salary? This never seems to be factored into the calculations.
Earlier quoted context omitted.
That was my first thought, too. Physical hardware == more staff. Also consider the risk management of keeping your security up to date, and the opportunity costs of making it easy to use for developers. Spend some time in old-school enterprise, and you'll see just how much pain and grief can happen. Remember, Amazon built its cloud not for the public, but for itself! The cloud gave them a clean separation of duties a…
With modern tools like Fully Automatic Install and Ansible/Puppet it shouldn't be any more than for a Cloud service.
Instant snowflake, just add expensive and archaic enterprise middleware.
If you only need five servers on the net, VPS' make sense (cheap, easy to spin new ones, etc...).
If you need 10, physicals (aka dedicated), might make sense. They're cheaper per Ghz, but take longer and need more skills to bring online.
Nees more? Colo might make sense.
Also, as you expand to physicals and colo, using some of the other options for specific needs might make sense.
http://www.wired.com/wiredenterprise/wp-content/uploads/2013... I guess "casual dress code" at startups these days means exposed feet on the table, right where your co-workers can see (and perhaps smell) them. And why does he have a roll of toilet paper under his monitor?
For use as facial tissues.
http://www.wired.com/wiredenterprise/wp-content/uploads/2013... I guess "casual dress code" at startups these days means exposed feet on the table, right where your co-workers can see (and perhaps smell) them. And why does he have a roll of toilet paper under his monitor?
To deal with crappy code?