| I can maybe give some idea of what he's saying about containers. We do use Docker, and when I mentioned in my original comment that I aimed to lower the skill required to come onto a project, Docker is the primary vehicle for that effort. Here are my reasons: 1. Nobody has to install dependencies. Docker is the only dependency (with compose). 2. Everybody has the same configuration. 3. Software versions are (mostly) tightly controlled. This requires whoever sets up the dev environment to make sure they use specific versions, and not :latest. 4. Devs don't need to spend time worrying about how the dev
environment works, just the code. This means that my README for a project usually has a section describing setup that just says: 1. run `dev/install` (any libraries from eg. NPM, go modules, etc.) 2. run `docker-compose up` 3. Check that the application is running on port XX. This actually works great, and it does allow new devs to get to work quickly, and it does allow us to use devs that know very little about the underlying software that we're using, unless something doesn't work correctly. And that does happen, much more often than I would like. Then it takes my time and theirs to get up and running, and that was definitely not the goal. |