DevOps for Humans in a growing business
When your business grows, it becomes challenging to remain open and transparent on every level of your operation. Developers will inevitably stack themselves on one side of the room, Operations on the other. Avoiding the well-known "Works For Me" and "Worked fine in dev, it's Ops problem now"-syndromes becomes difficult.
At Peytz & Co, we are approaching 30 Drupal developers distributed across offices in 3 countries. We also have an Operations crew of 3 full-time employees. Furthermore, we have Wordpress, Symfony and Ruby developers in the mix also, sharing some of the same resources. While we continue to put the needs of our clients and their users in the front seat, we must also maintain relations between colleagues and ensure that knowledge and information flows to the correct people at all times. We must do everything we can to maintain a sustainable ecosystem of tools, knowledge, feedback and human interaction.
This sesson will focus on the little things that we have done, are working on and have ahead of us, which all have the same goal: to allow ourselves to deliver the best possible product to our clients, and thus to the end users. It's all about people, on every level. Little changes like:
- Moving documentation from Google Docs and random READMEs to a unified platform
- Creating developer working groups to establish baseline company practices for Drupal, performance and more
- Dashboards!
- In-house Drupal distro
- KISS-based Vagrant+Ansible devboxes
- Ping-pong :D
- Feedback from production systems to lead developers
If you are in a company that wants to make developers able to deliver more robust Drupal sites, and at the same time improve human-to-human interaction (and frankly, who is not in such a company?), this session is for you. Simple changes from real life which aim to implement "Devops for Humans in a growing business".