While I might be missing the point of the article, and this may indeed be a people problem rather than one solvable with software, maybe a higher-level (one tha

While I might be missing the point of the article, and this may indeed be a people problem rather than one solvable with software, maybe a higher-level (one that is above rails, and above bundler, in terms of generic use) build tool could be of help here? I could imagine a command like `make fresh` performing these commands, noticing that things were missing, and informing the new dev of which way to go? Of course, documentation is the easier/possibly better solution to this problem, but It's a lot easier to standardize with less things to standardize on, and rather than trying to get every team to write good starting documentation, maybe making a mandate like "your repo must have support a make target called 'fresh' that will take a user from 0-setup to a fully setup environment, or print a useful error" [EDIT] - Also, some thoughts: -Is some of this pain actually good for Joe/Janelle? Could some of these issues be constrained as learning opportunities which might benefit them long-term (i.e. have a problem with bundler, find out about how bundler works)? -It seems like many (good?) engineering organizations with lazy (the good kind) developers will have solved this problem -- whether it's from the new dev wanting to save future devs trouble, or from the older devs wanting to save themselves time with env questions. -Docker is great, but I feel like getting the solution without experiencing the problem can hinder technical understanding. Docker compose is a breath of fresh air BECAUSE you have an easier way to boot, manage, and isolate related (in that they are all related to your app) processes. I would fear that varying levels of understanding would be allowed to just get by with `docker-compose up`