I'm currently at my first job, working at a budding unicorn company in silicon valley. I've been here 1.75 years and am already in the midst of a 3rd rewrite - although not my decision (from higher ups)
The last paragraph really hits home for me and i've 100% gotten very jaded and very very bitter.
Here's a really simple example of a project that I had set up using docker.
For my website I have it set up with continuous integration to run my tests when I merge into master and build a docker image which it then pushes to the docker registry. I then have it ssh into my host server, pull that image, then run the new container and remove the old one.
Boom, i've just deployed my website by simply merging a PR into my master!
This is just a simple use case, and I probably wouldn't suggest deploying a production ready site like this, but it's really cool! It's really simple to just pass around images and have things up and running on local dev's too
This is not something that is unique to docker though. I could just as easily set up a hook to deploy our site without docker, but it's not something I need.
I prefer to manually deploy, it's only one command, and I can make sure it's all worked correctly.
That said, I will be moving that command to a chat command, as I like that. But even then, it'll be a manually triggered command.
I have auto deploy setup for CI testing, as in that case I do want to know that those branches are ready for deployment to prod, when I want to.
Ahh that's true, I guess what I was getting at was that it makes the deploys much quicker and easier (at least in my experience).
I was also playing around with a chat command to spin up PR's/branches that haven't been merged into master yet, onto a temp container for viewing! Dunno, maybe i'm just not as familiar with other tools that can do similar things as easily
The last paragraph really hits home for me and i've 100% gotten very jaded and very very bitter.