4 ms·
This just doesn’t make sense. Google/Amazon employees basically are some random DevOps “dudes”. Whereas your own people would be...whoever you decided to hire t
by jrs95 8y ago
This just doesn’t make sense. Google/Amazon employees basically are some random DevOps “dudes”. Whereas your own people would be...whoever you decided to hire to work on your infrastructure.
- bootloop 8y agoIt's like an insurance. You wouldn't be able to hire as many and as highly paid random DevOps on your own. So you and others pay a 3th person to do it, just in case you need a competent person.
- leot 8y agoInfrastructure (ops, software, hiring, social) matters. Hiring some dude won't give you that.
- module0000 8y agoHiring the right dude will. The trouble is, most of them are happily employed elsewhere.
- allannienhuis 8y agoat AWS/Google? :P
- lameiam 8y agoyeah, by google and amazon.
- user5994461 8y agoThe right dude if both on week end AND on holidays right now. Please wait until Monday 20th to get a status on the issue. Thank you.
- devwastaken 8y agoProblem being that Infrastructure is made to be very, very compicated because they're selling tons of managed features that have reliance upon each other. I don't know why this idea of having your own devops is suddenly now bad. renting your own bare hardware and managing solutions yourself is still very much a thing and something you have to do if you're using lots of bandwidth. Dropbox for example made their own infrastructure to get off of AWS [1]. [1] https://techcrunch.com/2017/09/15/why-dropbox-decided-to-drop-aws-and-build-its-own-infrastructure-and-network/ https://techcrunch.com/2017/09/15/why-dropbox-decided-to-dro...
- hluska 8y agoI don't think that anyone thinks having your own infrastructure is bad, or if they do, they likely don't have much experience. Rather, I think it can be a nightmare if it's not properly managed, and it's hard to develop the skill to properly manage the process unless you've been burned in the past.