3 ms·
I would seriously reconsider this position. Containerization adds a significant amount of overhead to tasks that your team is probably already comfortable with.
by iandanforth 7y ago
I would seriously reconsider this position. Containerization adds a significant amount of overhead to tasks that your team is probably already comfortable with. It's not a clean, simple tool or abstraction as this article demonstrates. I've seen teams get eaten by docker hype and it's not pretty.
- dtjohnnyb 7y agoThanks for putting some brakes on the hype train! We're a pretty diverse team of developers with a wide range of skill levels and development environments. I was hoping that docker may have helped some developers get their environment up and running quicker and more standardised, but I can totally see how the opposite could happen if we're adding yet more overhead to the process. I'm going to keep tipping away at the idea in the background, since I've already learned a lot about building a better non-containerized version in the process, but I'm reconsidering the idea of rolling it out to the team.