We’re working to improve productivity, accuracy, and autonomy, which is especially important as we begin adding remote engineers. We wanted to reduce the cognitive burden of each engineer maintaining a development environment, so our engineers can focus as much as possible on the specific challenges and opportunities of our business. We are also evolving our production infrastructure towards microservices in Kubernetes and need an efficient and complete development setup in that context. When I heard the approach that these tools take, I was immediately excited to try it. The alternative is quite cumbersome.
Best practices around development workflow definitely take time to get right, they need to fit your organization, and they warrant a lot of consideration since they impact everything you do. There is no "one size fits all" approach. This is an ongoing process, it's important to continue examining (ideally, measuring) the way your team works, reflecting on it, and refining it. Testing your workflow with a small set of users, and incrementally rolling it out is a good strategy. Also, talk with the Datawire team on their Slack chat; they can provide good advice and perspective.