3 ms·
Check out vagrant[1]. I can have a new developer set up in about 30-60 minutes. [1] http://www.vagrantup.com/ http://www.vagrantup.com/
by redblacktree 13y ago
Check out vagrant[1]. I can have a new developer set up in about 30-60 minutes.
[1] http://www.vagrantup.com/ http://www.vagrantup.com/
- npsimons 13y agoI don't think the GP was referring to development environment setup time as a significant amount of the spin-up time of a software engineer. If it is, you've got bigger issues.
- raverbashing 13y agoWell, you're assuming that 1 - All projects can be run in a VM 2 - Setting the development environment is all a new developer needs Let me try to instil some expanded vision into things: - I can't have a VM for our specific embedded hardware with its specific devices - I haven't seen a VM for AIX on Power (maybe except running on Power HW) But most importantly, Vagrant can't put on the developer's head everything specific (s)he needs to know to do the job. Like how to use the proprietary utils that we need to integrate in a project. Or what the project is all about.
- redblacktree 13y agoI didn't mean to imply that Vagrant is appropriate for all situations. However, it has certainly been a boon to my web project. I hope you'll forgive me for misunderstanding "Just try and see how long until a developer has the development environment." -- The language is ambiguous, but "until a developer has the development environment" means software to me. That is, that the developer has the tools he needs to make changes to a code base. You're right that I may have taken too narrow of a view, but my interpretation also seems reasonable.