willthames
15 years ago I worked an infrastructure department with 50+ employees - these days a lot of that work that we used to do back then is taken care of by AWS.
Scaling the infra to meet peak capacity (which might be two days in a year) because you can only run on hardware you have, having data centres and data centre engineers, are all costs that go away with cloud, even though you are paying more for the compute you do use.
I had a quick search to find my favourite article on this one, it might be https://willgallego.com/2018/04/02/no-seriously-root-cause-i... as it demolishes Five Whys but https://www.kitchensoap.com/2012/02/10/each-necessary-but-on... is a classic
Being able to mount secrets and configmaps into the container file system (without having to modify the container image to provide an entrypoint) definitely seemed to be one major advantage of kubernetes over ECS a few years back.
The difference between datadog and doing it yourself is that datadog is a well thought through product rather than a cobbled together set of various tools
Having a single interface for everything makes life so much easier across a number of different teams
Search is fast and easy to use for logs and traces
Being able to see what a user actually clicked on in their session is absolutely game changing for support teams
I’m not a huge fan of the bill but it’s so much better than anything we could do ourselves without a team of engineers dedicated to observability (which would cost far more than datadog)
https://aws.amazon.com/about-aws/whats-new/2022/04/aws-data-...
https://www.gov.uk/dismissal/unfair-and-constructive-dismiss...
Of course it might not be worth the lawsuit.
There are plenty of caveats to the above (like the fact that the yum module won't downgrade [1], and you'll need reversible DB migrations) but that's basically the procedure.
[1] https://github.com/ansible/ansible-modules-core/issues/1419
But you can set the trackpad (Preferences > Trackpad > Point & Click > Tap to click) to accept a soft finger tap. And two finger tap is equivalent to a right click.
I think the MBP trackpad is the primary reason for me not moving to another laptop, even as I become less and less enamoured with OS X itself.
With hosted Github you have no choice - data will presumably live on mainland US. With Azure/AWS/whatever, you can host your data in the most suitable location (always worth checking the contracts though)
$ ls
hello_world hi_there_world
$ mv hello_world hello_everyone
$ !!:gs/hello/hi_there
mv hi_there_world hi_there_everyone
$ ls
hi_there_world hi_there_everyone* 250 user Stash license: $12000 first year, $6000 after [1]
* 250 user GH Enterprise license: $61750 per year [2]
If you need on premise git hosting, I'd look at Stash or Gitlab, long before I thought about looking at Github Enterprise!
[1] https://www.atlassian.com/licensing/stash#serverlicenses-1
The original post suggests ~$2000, not ~200k
They won't be 100% productive (50% might be aspirational for some roles for the first few months) and they will also reduce the productivity of their colleagues while they are brought up to speed.
$10k seems like a low figure for that.
If you do have an Operations person, you should be working together on things like how you can improve the deployment process to make it easy for new software to get into production.
If you don't have an Operations person, then you will have to bridge that gap. And that means learning what things make software operable - logging, monitorability, availability, resilience etc.
Web Operations, Continuous Delivery, Release It are three good starting points.
I gave a talk at Devops Days Brisbane on How to Design and Develop Software for Operations. I don't claim it to be complete but it comes from years of experience supporting critical applications
http://willthames.github.io/2014/08/10/devops-days-brisbane-...
There are likely existing roles for most things at http://galaxy.ansible.com/
The Ansible docs at http://docs.ansible.com/ are pretty good, and there are lots of getting started guides most weeks on the Ansible weekly mailing list (https://devopsu.com/newsletters/ansible-weekly-newsletter.ht...)
And there are a few pages on my github blog on a few fundamental principles of modelling configuration e.g. http://willthames.github.io/2014/03/17/ansible-layered-confi... http://willthames.github.io/2014/04/02/modelling-credentials... to give a bit of flavour of how to manage more complicated setups. Installing things is easy, getting the configuration right for your needs is the tricky bit!
If you mean 'please don't link to TV Tropes', say so.