3 ms·

I'm not sure why others are unimpressed with this article -- I thought it had one simple point to make. And my project has precisely this problem: people spend

• vinceguidry 11y ago
  Part of being a Ruby dev is learning how to quickly onboard. In the same way that as a C++ dev you need to learn your way around the output of configure and make, and be able to quickly figure out what error messages are telling you, you need to have that same baked-in knowledge of 1) pull the repo, 2) get the right version of Ruby installed 3) run bundle 4) install missing dependencies as bundler complains about them 5) run rails server and install backing services / configure environment variables as needed. 6) run tests and get them all passing. If you don't already have this knowledge than you're working with an incomplete set of tools and need to acquire them. The good thing is, if you're sharp, you'll pick up the general gist of things pretty fast. That's why I think nobody's yet written a guide encapsulating this knowledge. Docker is not the answer to the problem, it adds complexity rather than takes it away. You still have to know the ordinary way things work in case Docker breaks. I guess someone does need to write that guide, given how many people have issues with it, and the hopefulness evident in their pleas to just move to Docker already.