There is a dev tool for that.
Wherever you look there are new tools sprouting up by developers for developers. There is even a service for creating a notification bar on websites called HelloBar.
We have configuration management tools like Chef and Puppet, but now Salt Stack is getting some traction too. We have Github as the leading code repository/management service, but there is also an Enterprise SKU, and numerous other services like Atlassian’s BitBucket and Stash. The list goes on, chat services, project management services, continuous integration (test automation), PaaS, IaaS, etc.
This is a double-edged sword for developers. Having options is great so we can always pick the best technology for the problem. However, this creates a whole new world of pain.
On-boarding a new developer to the team takes weeks if not months as they have to ramp up on each of those services/technologies in addition to your company’s code base.
More tools means more overhead in dealing with each one manually.
Once we realize that the manual overhead is so high, developers start automating these process. This is an investment in performance, this back-end automation is never seen by customers, it does not generate revenue, and it’s time spent away from working on the product.
There is little integration between them, so automation comes in the form of glue code trying to piece together those services in finicky scripts.
After we invest in automation via code, we lock ourselves into those services as the cost of switching means re-writing a ton of that glue code.
These are the pains we felt as an engineering organization. Those were the pains that inspired us to create Factor.io. I’d love to hear how you have automated your deployment process, shoot us an email at firstname.lastname@example.org.