| Not so sure I really follow this.. I think you might be taking that to a bit of an extreme here. The problem you describe is the reason why we ended up with things like vagrant, and why docker is a good tool to get various setups to a 'common state' for work these days. Even with those tools though -- there are probably a few setup things that will need to run before I can start using these things and forcing everyone to use something they might not like/know just to make that setup bit quicker seems like shooting yourself in the foot. I'm a better developer when I'm working in my personalised environment (which I've been tweaking to my own and really specific requirements for over a decade, and that applies to most of us) than I am when being forced to adopt someone else's. We're a pretty picky bunch, some of us will want intellij and others emacs. Maybe someone wants to use BSD or Gentoo or OSX. You consider it radioactive toxic waste for devs to have their own work environment instead of adopting what the first person on the project uses? I'll conceed there might be a time saving in the first day on the project, but that barely counts in the bigger scheme. As an employer, I want my devs to work in whatever way they're most comfortable (and thus, productive) doing so. Forcing tooling across the board produces the reverse effect. edit: and not to be too harsh, but if your developers can't even run their code on their machines then perhaps you hired the wrong developers... |